Ok, so this is a bit of a cry for help. I'm not a non-techie, but am not massively familiar with this stuff - my first foray into trying to root my HTC One Mini has not gone so well so far.
First off, I unlocked the Bootloader as per HTCDev. On reboot, that left me in a boot loop, with just the htc splash, followed by a One Mini splash, then reboot.
Noting some others had had similar problems, I carried on following iconspiracy's method here: http://forum.xda-developers.com/showthread.php?t=2442043.
However, at step 9 of that, I was still in the same old boot loop. Spotting some advice that re-locking the bootloader would remove the boot loop, I foolishly re-locked it. Now it will only boot into the bootloader, and I am unable to get into the recovery. Help!? Any ideas welcomed.
Here is what is showing on the screen:
***TAMPERED***
***RELOCKED***
***Security Warning***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
RADIO-1.19.40d.00.14
OpenDSP-v13.2.0268.0620
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
then the usual bootloader stuff.
Thanks massively in advance!
Aha. Now re-unlocked and back in to TWRP. Would someone be kind enough as to suggest a next step - I'm a bit at a loss?
Well, I tried the same thing again, flashing the ROM and Kernel through adb sideload. Back to the same old boot loop.
Try doing a system restore, if that doesn't work try flashing a rom (Jmz's or MagioRom) in case yours somehow got messed up.
Returning to my phone this morning it booted, after a bit of a wait. Then I noticed SuperSU wasn't installed and went back into the recovery to do that. On reboot, back to that boot loop! Will try again after work.
asb56 said:
Returning to my phone this morning it booted, after a bit of a wait. Then I noticed SuperSU wasn't installed and went back into the recovery to do that. On reboot, back to that boot loop! Will try again after work.
Click to expand...
Click to collapse
Hey man! I know it's a hassle to get the phone to reboot until you're s off and relock the bootloader. I found it working better to power off and leave it off for a while and then power on instead of the regular reboot. It also helps if you do a super whipe and factory restore to be able to boot while your bootloader is unlocked.
HTC ONE mini
S-OFF
iconspiracy said:
Hey man! I know it's a hassle to get the phone to reboot until you're s off and relock the bootloader. I found it working better to power off and leave it off for a while and then power on instead of the regular reboot. It also helps if you do a super whipe and factory restore to be able to boot while your bootloader is unlocked.
HTC ONE mini
S-OFF
Click to expand...
Click to collapse
Thanks for replying! I did manage to get it to boot once more, but then I decided to see if that was a stable state - no dice, back to the loop.
Weird thing is, if I re-lock the bootloader at this point, I can only boot to the bootloader.
By the way, here's what I've done (anything leap out as wrong?):
boot into TWRP
wipe Dalvik, Cache, Data, System
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's stock Odexed WWE ROM)
boot into TWRP, set up sideload
adb sideload ROM.zip (using the same ROM)
wipe dalvik, cache
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's Kernel)
boot into TWRP, set up sideload
adb sideload Kernel.zip (using the same Kernel)
wipe Dalvik, Cache, Data
Try to boot (=bootloop) / re-lock bootloader and try (=boot to bootloader only)
asb56 said:
By the way, here's what I've done (anything leap out as wrong?):
boot into TWRP
wipe Dalvik, Cache, Data, System
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's stock Odexed WWE ROM)
boot into TWRP, set up sideload
adb sideload ROM.zip (using the same ROM)
wipe dalvik, cache
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's Kernel)
boot into TWRP, set up sideload
adb sideload Kernel.zip (using the same Kernel)
wipe Dalvik, Cache, Data
Try to boot (=bootloop) / re-lock bootloader and try (=boot to bootloader only)
Click to expand...
Click to collapse
Boot into TWRP
Whipe cache, system, dalvik and data
Flash the odexed JMZ rom via sideload
Wipe dalvik and cache
Flash JMZ kernel
Boot into bootloader and flash kernel boot.img via fastboot
Boot into TWRP and install superSU binaries via sideload
Wipe dalvik and cache
Reboot system
Might have a few bootloops before you get booted correctly!
When you're booted into android you'll see a message telling you Androind is updating! When that's done you get into the setup phone process! Don't do anything here not even connecting to wifi maybe just selecting what carrier settings you want if that option appears. Because next you'll probably get an OTA notice and if you're connected to wifi you're screwed cuz you'll only have the option to download it and it will install it and it didn't work for me so I suggest you stay away from it as well.
After that without any reboot open the superSU app and make sure you see that it's installed correctly. When that's done you're successfully rooted and you can download revone from your phone and it will be downloaded to your downloads folder on your sdcard. You also need to connect to play store and download a file explorer that can handle root privileges like root explorer and also install terminal emulator from play store.
Open root explorer and move the revone file from downloads to /data/local/tmp
Open terminal emulator and type su
Grant the terminal root access when the superSU popup shows and ask you that
Type the command cd /data/local/tmp
Type the command chmod 775 revone (might be revone.bin just use the exact name here)
Type the command ./revone -P
You'll probably get the message "error code: 2" here but here it's time to make your phone reboot and I suggest you turn off your device and wait for a minute and then turn it on again. The phone should boot up but you might have a few loops but just wait for it to boot up properly. Once you're back into the OS start the terminal emulator and type the following commands
su
revone -s 0 -u (remember to use the exact name of revone here as well. If it's revone.bin you use that!)
Now you should get the message that revone was successful and you can reboot into bootloader and relock your bootloader and then reboot the system
It will boot up normally now and you can run the command revone -t to remove the tampered flag now
Hope this helps
HTC One Mini
S-OFF
---------- Post added at 09:59 PM ---------- Previous post was at 09:53 PM ----------
Just to clarify use the exact name of the revone file in every command that includes revone! Make sure you include the file extension if there is one!!
HTC One Mini
S-OFF
Mega thanks. Will try when I get a moment - trying to move house at the same time.
Do you suppose it's actually necessary to be S-OFF to fix this boot loop? I mean, I can re-lock and re-unlock without that no probs...
asb56 said:
Mega thanks. Will try when I get a moment - trying to move house at the same time.
Do you suppose it's actually necessary to be S-OFF to fix this boot loop? I mean, I can re-lock and re-unlock without that no probs...
Click to expand...
Click to collapse
You probably don't generally and you can try without the s-off part but when you're s-off you can do all the things you want even with the bootloader locked
Skickat från min C6903 med Tapatalk 4
Related
I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
obg8 said:
I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
Click to expand...
Click to collapse
If you are s-off you shouldn't need to flash the kernel seperately.. However use "fastboot devices" instead of "adb devices". When you are connected to a computer via USB it should indicate that on the bootloader.
Before I was s-off I'd flash the rom then return to the bootloader directly and flash the kernel before attempting to boot for the first time.
The post above mine is correct. If you are s-off you don't have to flash the boot.img. Going by what you posted it doesn't look like you wiped your data in recovery, which is something you have to wipe when flashing a new ROM. That's probably why it didn't boot properly. Try again doing a full wipe/factory reset from recovery.
Sent from my One X using Tapatalk 2
Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?
You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...
Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:
ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.
...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.
Hello everyone,
I am asking for help because my Nexus 5 stuck into bootloop suddenly. My phone is unrooted, bootloader in locked state, as I have never flashed any ROM in my phone. I am not keen on getting the files in my phone back but just want to use the phone again. I have tried many methods to restore my phone but still, I failed. I can go to fastboot and recovery mode. However, my phone is still in locked state, I could not flash any factory image into it using Nexus root toolkit nor put any rom files to sdcard. and I couldn't unlock the boot loader as it is in a boot loop. Do anyone got any ideas to save my phone, please help me.
P.s. I have already tried the following methods:
Method1 ( Failed because my phone is in locked state, cannot push any ROMs into it.)
-setup ADB, connect phone while its in recovery to adb.
-Download a rom for your phone (you can head over to XDA to look for rom and download one you like). Just download it to your pc.
-Connect your phone to pc using USB.
-Open cmd and enter the command adb push PathAndNameOfROMFile.zip /sdcard/. This will push the rom file you downloaded above to sdcard.
-Wipe your system, dalvic cache, cache and data (recommended, but not necessary if you downloaded same rom as previously installed on your phone).
-Reboot.
Method2 ( Failed because my phone is in locked state)l, cannot write any ROMs into my phone)
Semi-Case 2:
-There is some problem flashing some specific part.
-In this case, you can try flashing manually.
-Run these commands One by One in cmd/terminal (replace C:/ with path to where you extracted the official factory ROM archive):
fastboot flash bootloader C:/image-hammerhead-xxxx/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-xxxx/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-xxxxx/system.img
fastboot flash userdata C:/image-hammerhead-xxxxx/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-xxxx/boot.img
fastboot flash recovery C:/image-hammerhead-xxxx/recovery.img
(Skip the above command if you dont want to flash stock recovery and are sure that your current recovery is not corrupt).
Fastboot erase cache
-This will manually flash everything. Hopefully this time it should be fine.
If you can get into recovery try wiping your cache from there. Try more than once if it doesn't work the first time.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
If you can get into recovery try wiping your cache from there. Try more than once if it doesn't work the first time.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
I have tried that for a few times, but a flashing recovery mode android logo appears after I wiped the cache.
Unfortunately you may have to unlock your bootloder and reflash the firmware. Not that difficult but will wipe your phone so you will lose any photos or data that you may have on it.
frenziedfemale said:
Unfortunately you may have to unlock your bootloder and reflash the firmware. Not that difficult but will wipe your phone so you will lose any photos or data that you may have on it.
Click to expand...
Click to collapse
Thank you for your advice, I don't mind losing the data. I have tried unlocking the bootloader but when my phone is unlocked using Nexus Root Toolkit, it goes into boot loop and become locked again when I goes into fastboot mode.
Hey. I just flashed a stock rom and re-locked the bootloader, in order to unlock it, get twrp, get a custom rom (likely lineage) and root with magisk (it seems better than superSU, no?) without any toolkit, because i want to get some knowledge about android.
I downloaded adb and fastboot, enabled USB debugging, booted my nexus 4 on bootloader mode, and I used 3 commands after opening the command prompt from the folder containing fastboot. I also downloaded the latest img of TWRP for nexus 4 and renamed it "twrp" and put it on the folder.
The 3 commands I used are : "fastboot OEM unlock", "fastboot erase recovery", "fastboot flash recovery twrp.img"
But when the phone tries to boot the recovery, I get this : puu.sh/wWTjC/6cf11a9a32.jpg
and it doesnt work ofc.
Furthermore, I can't boot the ROM, I can only boot the recovery and the bootloader. When I try to boot the Rom, i get the recovery.
can someone help me please?
thanks
Hello,
The problem is that the recovery is unable to mount the /data partition, what you need to do is repair it by the following steps
1.Go to TWRP main screen
2.Press wipe
3.press advanced wipe
4.tick data
5.press repair and change file system
6.press repair
7.wipe the arrow
NOTE: this will format the data partition
now reboot to recovery again and check if the problem is fixed
Hello, the problem is I cant reach the main menu of TWRP, after getting what I screened, my phone reboots on TWRP again, and again...
I also tried the command "fastboot boot twrp.img" and i get the same result.
where did you get the twrp from ?
i would in such case as twrp is having troubles first try to find a working version of it, and it it didn't work i would reflash to stock stock and start from scratch
I got twrp there : dl.twrp.me/mako/
i took the latest version.
Get the cwm recovery for your device, wipe data , then try reflashing the twrp recovery
It's ok, thanks
nublord said:
It's ok, thanks
Click to expand...
Click to collapse
did that help ? hopefully?
hmm, I thought it did, but i actually get the same problem, and I can't launch neither cwm nor twrp..
Once yo reinstall twrp
Go to wipe the format data to remove encryption
You can also use cwm to flash the ROM