Develop Bugs

[Q] Can't use su, can't turn on root. All I want is a full wipe.

Hello.
The screen of my toro is completely destroyed. It's shattered and the ribbon cable is torn, so no touch input and no image. The rest of the hardware is in tact and working perfectly fine. I want to sell this for parts, but want to wipe all of my personal data before doing so.
I'm running CM10. Using su in ABD, as expected, says "Permission denied" because root is not enabled in developer settings. I cannot enable this using the touch screen because it does not work at all. I figure I can plug in an OTG keyboard and count my key presses, or similarly boot into recovery and count my clicks of the volume rocker.
But once I'm here I'm not entirely sure what to do honestly. Is there a CWM installable package that resets everything to factory settings? I emptied the sdcard directory from ADB but I'm afraid personal information exists elsewhere on the device as well.
Any help here would be appreciated.
Thanks!

Gleasonator said:
Hello.
The screen of my toro is completely destroyed. It's shattered and the ribbon cable is torn, so no touch input and no image. The rest of the hardware is in tact and working perfectly fine. I want to sell this for parts, but want to wipe all of my personal data before doing so.
I'm running CM10. Using su in ABD, as expected, says "Permission denied" because root is not enabled in developer settings. I cannot enable this using the touch screen because it does not work at all. I figure I can plug in an OTG keyboard and count my key presses, or similarly boot into recovery and count my clicks of the volume rocker.
But once I'm here I'm not entirely sure what to do honestly. Is there a CWM installable package that resets everything to factory settings? I emptied the sdcard directory from ADB but I'm afraid personal information exists elsewhere on the device as well.
Any help here would be appreciated.
Thanks!
Click to expand...
Click to collapse
you could fastboot the images as you do not need the touchscreen to do so.

Zepius said:
you could fastboot the images as you do not need the touchscreen to do so.
Click to expand...
Click to collapse
Thank you for your help. I've never used fastboot before.
I ran:
Code:
adb reboot bootloader
and waited for several minutes. Then:
Code:
fastboot devices
and no devices are detected. ADB detects my phone when I boot normally.

Gleasonator said:
Thank you for your help. I've never used fastboot before.
I ran:
Code:
adb reboot bootloader
and waited for several minutes. Then:
Code:
fastboot devices
and no devices are detected. ADB detects my phone when I boot normally.
Click to expand...
Click to collapse
you dont have the fastboot driver installed.
there's a post in general about how to return to stock with the drivers there.

Zepius said:
you dont have the fastboot driver installed.
there's a post in general about how to return to stock with the drivers there.
Click to expand...
Click to collapse
I'm in Ubuntu, I didn't understand how fastboot worked and downloaded a precompiled binary without realizing I already had it in my platform-tools folder... pretty stupid.
I used fastboot to erase each partition individually with:
efrant said:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Click to expand...
Click to collapse
And am reflashing the stock ROM. Thank you so much for your help!

Can't format /data & /cache

Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.

Leshy01 said:
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Click to expand...
Click to collapse
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?

cmlusco said:
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
Click to expand...
Click to collapse
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.

Leshy01 said:
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Click to expand...
Click to collapse
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.

cmlusco said:
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.

Leshy01 said:
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Click to expand...
Click to collapse
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc, and select fastboot from the hboot menu, so that it says fastboot plug in red at the top. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
fastboot devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.

cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.

tiny4579 said:
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
Click to expand...
Click to collapse
Thanks tiny, you do great work yourself. I like helping people and i love technical stuff. Knowledge is everything, and its good to pass it on.

cmlusco said:
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
adb devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
Click to expand...
Click to collapse
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?

Leshy01 said:
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Click to expand...
Click to collapse
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
I do not know of an irc channel, and i like to keep the conversation here so that the instructions and common issues and fixes can be seen and learned from by others.

cmlusco said:
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
Click to expand...
Click to collapse
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.

Leshy01 said:
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Click to expand...
Click to collapse
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?

cmlusco said:
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
Click to expand...
Click to collapse
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.

Leshy01 said:
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Click to expand...
Click to collapse
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.

cmlusco said:
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
Click to expand...
Click to collapse
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2

cmlusco said:
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Click to expand...
Click to collapse
Well... I'm sketchy on the exact terms here, but In CWM, I can mount the drives without getting any errors, but whenI try to format I get errors. I haven't actually "done" anything with those partition besides that.
However. I ran through ALL the steps you had me to. Flash the stock ROM w/ recovery, unlocked bootloader from HTC, pushed all the filies you had me through adb. After all that, I flashed CWM, then I flashed CM7, and then I booted up my device. As if my /data partition was not touched, all my apps were still there (titanium backup, my google accounts were still setup, app data and settings were untouched). So on a whim, I ran titanium backup, and uninstalled every single user app (since the android native uninstaller force closes). I ran it successfully, rebooted, and every other app was still there.
So it can READ the /data partition, but I have no abilities to MODIFY that partition. Through any recovery or formatting.
tiny4579 said:
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm willing to try anything because at this point nother else works, but I don't know where to start. And even if I find some documentation about other devices' partition table setup, I'm assuming the Incredible is different. Way I see it, I can't mess it up any more than it already is.
I'm hoping you guys have some sort of answer, but I'm looking around elsewhere, and I really appreciate everything you guys have contributed to this thread, and the community. Thanks!!!!!

Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?

megosu said:
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Click to expand...
Click to collapse
I don't think the mmc bug has anything to do with the Droid Incredible or even affects it. I thought the mmc bug led to a fully bricked phone.
This isn't really the thread for this but have you tried the full Odin Factory reset for your device which includes the /data partition? I think the method that uses a PIT file is the most thorough but most risky. I recommend posting any questions in your device's thread but I've had a few samsungs and am somewhat familiar with that process.

I think I may have ruined my phone

Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery

haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?

Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.

MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found

haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.

now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps

mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?

haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/

haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)

mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.

haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups

BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone

haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc

BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either

haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps

BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much

haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:

BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

Honor 7x with Lineage and TWRP, stuck in limbo

Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?

Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32

It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?

Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen

I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.

Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk

Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works

smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use

dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot

Please can you tell me the process to install twrp I have the L24

I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.

I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?

Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.

I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.

Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.

I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).

Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?

Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.