hello, i was wondering whether i could safely temporarily boot TWRP on my 6.0 android in order to root it. the phone's model name is e-boda eclipse g400m, and as far as i can tell there's no rooted rom for it out there, so as far as i know, that's the only way (i can't edit the rom because the programs take way too much space for my ssd).
to be more specific, my phone is not on the supported device list, but since it's "temporary" booting i assume it's safe to try without a chance of bricking my phone. however, i don't want to take the chance, so i decided to ask here first.
If the device has fastboot mode then you can use the boot option instead of the flash command to temporarily boot a recovery image.
yeah, i enabled fastboot, but i'm asking whether temporarilty booting in a custom recovery that most likely doesn't support my phone will brick it or not.
if recovery mode gets bricked and you have an unlocked bootloader, I don't think that would brick the whole device.
Related
Hi, just thinking about how to recover bricked hero's. Firstly i think only possible unbricking process would be if the phone has been rooted.
I am listing some possbile methods.
Method 1:
NOTE: Only works if you have backed up your NAND (Nanroid file somewhere)
Start the phone in recovery mode and flash your original NAND file and in theory this should unbrick the phones. After this you could just flash the phone with generic HTC Rom just to be safe.
Method 2:
Reflash the phone with recovery image from Cyanogen. Than reflash with a ROM possibly HTC generic rom.
NOTE: These are only possible (thought to be ways of unbricking)
If you can get into recovery mod and flash a ROM then the phone isn't bricked.
Just....broken
Fair enough, but i have heard it is still possible to get into recovery mode directly or even via SDK
You can often get into Recovery, you wouldn't be able to do anything with it though
i thought the only way to unbrick a phone is to jtag it?
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
Hello everybody,
Im totally new and have a big problem.
I rooted and unlocked my phone (HTC one m9), to install a costum Recovery (Team win)
I followed all instructions and copied viper rom on the phone.
After installation, I got into the bootloop.
I can see white HTC Bootscreen with the red instruction ..."This build is for..."
I know, that my phone is not able to boot new image because S-Off is not enabled.
Now my question.
Whats the best way to get a solution for this problem.?
I can boot into download mode or get into my costum recovery.
ADB and platform tools are installed on computer.
Need help. please!!!
Factory reset seems to be it. Thankfully something pops up, instead of dead. There should be a option( you may have to look for it on xda) to get into the stock recovery, through a combination of button presses. On my phone, volume up, and power button gets me into twrp, volume down and power button takes me to the stock recovery. You may have different cadence for your particular phone, so finding that out is a must to return to stock, which you can start over again. I couldn't even root my phone, with out installing twrp first, so I had to get the unlock code, to unlock it first. Some phones may have a different way to root, without unlocking the bootloader first, but start over, it still turns on. Whatever you have had will be lost, if you didn't backup somewhere before you started to install twrp, because it won't boot into the os, that info's gone, and you have to go back to stock, to get rid of the garbage that would still be there from the failed attempt. Trying to install twrp, without doing that may corrupt your partitions, then it may get bricked beyond repair.
What are the necessary steps i have to follow?
Relock Bootloader?
Flash firmware.zip?
how do i flash stock rom?
Im not able to star my phone.
only workspace is recovery and ADB via PC...
Help please!
Hello all,
I recently bought a Archos Safe T Touch (because it was dirt cheap at the time, don't juge me). I know it's a pretty useless device even for cryptobros (I'm not) but I was hoping that I could hack it, built TWRP, install GSI and make it my device for 2FA authentification keys.
But, it's hard to unlock a device that have an amputated android image. This means no way to graphically get to the launcher, settings, oem unlock nor adb.
But I did succeed to unlock bootloader thanks to https://github.com/bkerler/mtkclient .
And since Archos give generously the stock rom and sp flash tool files https://update.archos.com/safettouch/SafeT-touch-Upgrader-v1.2.5.zip?fw=latest https://update.archos.com/safettouch/Changelog-v1.2.5.txt I'm able to flash system, boot or recovery img.
So from there I tough I could flash TWRP (I build myself one) but I can't get to recovery nor fastboot mode, this device lack volume buttons.
So plan B I flash GSI (LineageOS android 10) but the partition is too small and sp flash tools refuse to flash it.
So plan C I try to patch boot.img with magisk from another device. It does not boot....
So I'm kinda stuck at this point, I'm fresh out of idea...
Ho and in my tweaking journey I burst open the glass-ish back panel (it cannot be dissemble cleanly, or you need some expert tools), to access the battery.
So please come forward if you succeed to do anything with this device or if you got some ideas