M9: TWRP, No OS, (system 0mb) - One (M9) Q&A, Help & Troubleshooting

Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco

Fryslanboy said:
Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-one-m9/help/bricked-issues-return-to-100-stock-t3547433
Read my thread hope this helps.

Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)

Fryslanboy said:
Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)
Click to expand...
Click to collapse
That is weird. Did u format data in TWRP by typing Yes, not just factory reset?

Well, I can't get into TWRP anymore. When I select Recovery in the fastboot menu, it goes to the black HTC screen, after that quick flash of the TWRP screen (it worked before) and then it goes to it's white HTC screen.
I'll try to install TWRP via fastboot, maybe that'll help

Just tried to flash TWRP through fastboot, which was finished, but I still can't access Recovery. Weird..

You haven't stated if you are s-off. Have you made sure the stock rom matches your sku?.
Beamed in by telepathy.

Yes,
I am S-OFF. I tried several rom's, but I'll double check that. Good point!

Related

[Q] Please help - Desire very poorly.

Hi. I hope someone can help.
I've been using my desire rooted and S-OFFed running Defrost for sometime, all has been fine. Was playing Angry birds yesterday and the phone froze.
Pulled the battery and rebooted, carried on playing. Froze again.
Pull the battery again but phone stuck on the first splash screen. Fiddled a bit, couldn't get into recovery. So I left the phone on charge until the light went green, then removed the battery and left it overnight.
This morning I put the battery in and switched it on. It booted fine, but froze when I tried to unlock it.
I've tried pulling the battery again and again. I can get into HBOOT, but the phone isn't recognised for ADB or fastboot commands via USB. It often freezes even in fastboot mode.
I tried to do a clear storage, but that froze as well. Although a subsequent attempt appeared to work but the phone still won't boot normally.
So I can't reflash or do anything else. HAs anyone actually sent a phone back for repair with custom firmware/splash screen installed, as I don't think I'm going to be able to revert it to stock.
I've tried numerous restarts with and without a sim and an sd card inserted. Not sure what else to try.
Any help greatly appreciated.
did you wipe the dalvik cache through recovery?
try this if you can.
No I haven't wiped the dalvik cache. I have managed to get in to recovery on a couple of occasions. But the phone has frozen again navigating the menu.
I will try that if I get into recovery again though.
Thanks
Quick update.
After leaving the battery out for a couple of hours. I tried again and the phone started to boot. It got to the splash animation and the wipe had obviously worked because it was the DeFrost default of the X. This then looped a few times then froze.
I pulled the battery and managed to get in to Clockwork Mod recovery and did a wipe from there, which appeared to work, but then it rebooted by itself and I still didn't manage to do a dalvik wipe.
Now I'm back to the same point again. I can't get into recovery.
I guess I'll try again after leaving the battery out for a while.
One thing I did notice when in recovery was that the trackpad didn't work. I had to use vol and power keys. If I get into recovery again, I'll try a keytest if I get into recovery again.
And another update.
I got into recovery again and did a wipe dalvik cache.
I got the following error.
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Dalvik cache wiped.
So I'm not sure if it actually did it or not.
I then tried to do a nandroid restore and got a similar error.
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Then the phone froze again.
So I'm guessing something is corrupted here.
Should I try formatting the SD card. (I have backed up all the data I could using my PC).
i think your dalvik will have been wiped. i always get the same message.
have you tried it again but without trying to restore a nand?
Yes, I tried it again. I only seem to be able to get in to recovery after leaving the battery out for a while.
This time I did a dalvik wipe then rebooted, but it's just stuck on the initial splash screen again.
I'm pulling my hair out here (what little I have)
have you considered going back to a stock rom using an RUU or PB99IMG?
then you'd have to root again and restore your nand if possible/needed.
I'd be happy to try reverting to stock, but don't you need to get the phone to boot before you can do that?
I have sent this phone back for repair previously and done just that (it suffered from the overheating problem and had a whole new motherboard less than months ago).
After leaving the battery out again for a while, a normal switch on got to the animation splash then rebooted twice before freezing again.
Is this likely to be a corruption in the flash memory, or a hardware problem?
Hello,
I've got exactly the same problem! The phone freezes on the first splash-screen (not the Rom's bootanimation) and I can't get into recovery.
I'm running Oxygen Rom (2.0-RC6) and using Apps2SD in combination with an 8GB Transcend microSD card. I've only "rooted" it once using Unrevoked (long time ago), so I assume it is still S-On. I'm using clockwork's recovery, too.
At the moment I really don't know what to do.
What could I try?
pc99mk:
At the moment I'm leaving the battery out the phone until afternoon, hoping to get into recovery
Thank you in advance for every bit of an answer
Read up on the PB99IMG process if you can get into recovery (power & vol down).
Otherwise, the RUU will work if you can boot into fastboot (power & back key).
Sent from my HTC Desire using Tapatalk
Hi spadoleo.
Sorry to hear you're having similar troubles.
I'm sure mine must have some sort of hardware problem now.
After leaving the battery out for a while again last night, I managed to get into fastboot and flash the latest alpharev hboot, and clockworkmod 3.0.0.5 in the hope that my freezing problems there were due to a slight corruption.
Clockworkmod has definitely updated as the colour of the menu has changed, but it still freezes soon after entering.
I just want to try and get the phone looking as much like a stock phone prior to sending it back now.
Does anyone have a fasstboot flashable image of the following:
UK TMobile 'Pink Circle' splash1 image
Standard HBOOT
Standard recovery
Otherwise I'm just going to have to send it back to HTC as is, and hope they still fix it under warranty.
Or is there any way of getting a RUU to start doing anything with the phone in fastboot?
Or indeed anything else I can try?
See my post above.
You can run an RUU in fastboot.
Sent from my HTC Desire using Tapatalk
Hi mikep99.
Ok thanks for the advice. I'll have a read of the pb99img stuff.
I tried the RUU this morning in fastboot mode, but every time it justs sits at the 'Verifying information on your Android phone' for a while, then times out with a USB connection error.
I seem to have best results after leaving the battery out for a while (no idea why that should make any difference but it does), so I'll try it again in an hour or so.
Cheers
Install htc sync if you haven't already.
And try turning off antivirus and firewall on your PC
HTH
Sent from my HTC Desire using Tapatalk
Ok. I read up on the PB99IMG process.
I found a PB99IMG.zip file posted by Teppic74 which is a stock Froyo.
I copied it to the root of my goldcard and booted the phone.
It loaded the file and came up with
Incorrect CID error
update fail
I then kicked myself. I created the gold card to revert the phone to stock before sending it to HTC previously.
They replaced the motherboard. Would this have changed my CID?
I then thought 'no problem I'll just go through the gold card creation process again'
But although I can do stuff on the phone in fastboot mode, adb doesn't work in that mode. So trying adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
just gives an error.
So if my CID has changed, any idea how I can create a gold card with the phone in this state. Should adb only work when the phone is booted, or should it work in hboot or fastboot?
i'm not sure which PB99IMG you're trying to flash but i'd use this (if its not the same):
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
with regards to the goldcard, have you mounted the sdcard when in recovery? and then running
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
again?
if that doesn't work, you can use another TMobile Desire to create it.
therefore, i don't think the mbo change should affect your goldcard????
EDIT - when you got your phone back from repair, was it completely wiped? Tmobile may have wiped/swapped etc.. the goldcard you previously made.
I think it was that image that I used. But I'll download it again just to be sure.
When the phone was repaired before, I sent to HTC directly and I didn't send any sd card or battery. So it should still be as it was.
So if the CID isn't motherboard specific it should still work.
Is there any way to check whether it is still a goldcard? I may have formatted it again (don't recall).
Although thinking about it, I still have the image file emailed to me when I created the gold card originally, so I could just reapply it and try again.
I'm out tonight, but will try a few things and post back with my results.
Thanks for your help so far.
Another update and things have moved forward.
It turned out I'd trashed my gold card, but I did still have the image file so I recreated it.
I then booted the phone again and it loaded the PB99IMP.zip file.
It then asked me if I wanted to perform the update. I said yes, and it updated the bootloader and rebooted. Then it froze on Checking PB99IMP.zip....
After leaving it 10-15 minutes I pulled the battery again and left it for a while.
I tried again just now.
I can see that it has updated the HBOOT, so I'm no longer S-OFF.
Just now I thought it was going to work it got about halfway through updating the system partition before freezing.
If only it had updated the splash1 image before the system, I might've had the phone in a suitable state to return. But it still shows my custom splash1 screen when powering on normally - then it changes to the piccy with the green arrows.
I'll try it again later after leaving the battery out for a while.
But the fact it freezes in the middle of such an update suggests it's definitely a hardware problem of some sort.
If anyone has any other ideas I could try, please let me know. But once again thanks for all the help so far.
Sounds like you're getting somewhere
Just keep on trying every now and again.
Hopefully it'll go through...
Sent from my HTC Desire using Tapatalk

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

2017 LG G4 Stuck in Boot Loop?

I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.
Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs

Extreme Bricked Honor 7X BND-L21

I have completely bricked my phone. It does not have a functional screen or anything anymore. It is stuck in fastboot and wont leave it in any way.
How this happened:
I tried rolling back to an older version via HiSuite DNS spoof to EMUI 8 again, but it failed to boot after that. It has been stuck in fastboot since then.
I DO have the bootloader and FRP unlocked. I already did that via the test point method. Anyone got any ideas what i could do now?
I already tried flashing system, recovery, cust and ramdisk, did not help in any way. I'd appreciate some help.
I have also tried downloading Full OS from TeamMT but it seems to reset after 300MB being downloaded.
I got the screen working again but its constantly rebooting into this screen now
MrRobBoss said:
I got the screen working again but its constantly rebooting into this screen now
Click to expand...
Click to collapse
If you are able to boot into recovery, you could try service rom from here, (OTG cable or adaptor)USB formatted as ExtFAT and dload folder with required content, then 3 button combination. Double check if makes any sense.
hardcorehenry said:
If you are able to boot into recovery, you could try service rom from here, (OTG cable or adaptor)USB formatted as ExtFAT and dload folder with required content, then 3 button combination. Double check if makes any sense.
Click to expand...
Click to collapse
I tried booting into recovery but it keeps on booting into error mode. I have not tried if it fails test point aswell but currently not able to test it.

Categories

Resources