my hero has keeping restart .
the list what i do :
1 . update 2.1rom
2.SPC --unlock
3.write the esn and imsi and a-key
4.then my phone keeping restart
5.use ruu 1.56 recovery,has the same result
what could i do ?
can you boot into recovery!?
before i use ruu1.56,the recovery is good ,now ,it doesn't work again.
when i get into root screen ,select the recovery ,then ,the phone display the Triangle warning sign
galaxyzhang said:
before i use ruu1.56,the recovery is good ,now ,it doesn't work again.
when i get into root screen ,select the recovery ,then ,the phone display the Triangle warning sign
Click to expand...
Click to collapse
reflash your recovery image via adb, and nandroid back!!
somebody told me try the ruu1.29,to Resume Original state,it seems 2.1 rom can lower to 1.56,but can't to 1.29 .
another details :my phone restart ,first display:"no service",if the Problem is the signal module, or it was bad ESN? Lead to restart the phone non-stop?
galaxyzhang said:
somebody told me try the ruu1.29,to Resume Original state,it seems 2.1 rom can lower to 1.56,but can't to 1.29 .
another details :my phone restart ,first display:"no service",if the Problem is the signal module, or it was bad ESN? Lead to restart the phone non-stop?
Click to expand...
Click to collapse
sorry thats too deep for me. am i understanding you correctly; you used the 2.1 RUU?
try and boot from your sd card lmao!
seriously, can anyone find that thread? that would be a great read.
mountaindont said:
reflash your recovery image via adb, and nandroid back!!
Click to expand...
Click to collapse
how ? is there some guide ?
thank you !
galaxyzhang said:
how ? is there some guide ?
thank you !
Click to expand...
Click to collapse
um yes. in the guides thread.
sticky wiki!
LOL! Is this **** for real?
This is how to do it. Download a recovery image (Amon_Ra, ClockworkMod, GodSpeed), name it "recovery.img" and put it on the root of your SD card. Then, run these commands (i'm assuming you have ADB).
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery.img
reboot recovery
It will be slow in the flash_image command, don't freak.
HeroMeng said:
This is how to do it. Download a recovery image (Amon_Ra, ClockworkMod, GodSpeed), name it "recovery.img" and put it on the root of your SD card. Then, run these commands (i'm assuming you have ADB).
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery.img
reboot recovery
It will be slow in the flash_image command, don't freak.
Click to expand...
Click to collapse
Thank you very much!
I did what you told me ,but when i type the last cmd ,
the result :flash_image :not found
what the problem?
did you have the file in your sd card?
macvalentine said:
did you have the file in your sd card?
Click to expand...
Click to collapse
yes.i copy the recovery.img to the sdcard
maybe i used <RUU_Hero_C_Sprint_1.56.651.2_signed_release> damaged the recovery mod.
Related
Okay so i've been at this some time, following
Guide to root Rogers G1's
http://forum.xda-developers.com/showthread.php?t=532419
now my phone is currently stuck at the rogers screen with the fastboot usb at the top left corner, and i've uninstalled the drivers and re-installed, and when i do the cmd for adb devices
it shows
List of devices attached
^ nothing.
am i installing the driver wrong? its showing on the usb as Android 1.0 after i go and select the x86 driver, currently running windows 7 . If you could please post some help i've been reading since yesterday and can't seem to get passed this issue
i beleieve the main issue would be me not being able to access my sd card, anyway to push a file through onto it somehow via cmd adb ? if so, tips would be great , my sdk is in c:\android\sdk-windows\tools and i have it up and running in cmd. Please help .
Update: i was just able to
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
and boot into "Android system recovery<2>
[Home+back] Reboot System now
[alt+s] apply sdcard:update.zip
[alt+a]apply any zip from sd
[alt+w]wipe data/factory reset
[alt+b]nandroid v2.2 backup
[alt+r]restore latest backup
[alt+f] erpair ext filesystems
[alt+x] go to console
now i know the only file on my sd card is the spl renamed to "update.zip"
no rom on it , so how do i get the rom on it from this point? any help would be great, leaving it at this screen until further notice from boards.
also note, bottom of screen says
"Build: CyanogenMod v1.4 + JF
Formatting CACHE:...
Nothing moving
PLEASE Help :'(
Thanks
do you have a recovery image installed? and whats the current rom that you are on?
Shaquiel Harris said:
do you have a recovery image installed? and whats the current rom that you are on?
Click to expand...
Click to collapse
I beleive what i've done is erased the default rogers rom on there, and during flash attempt, wiped it, now there is no rom on it , so i have this cyanogenmod 1.4 +JF on here, and can't access my sd card, anyway to do it from the current menu i'm on ?
There is only the spl on my sd card root (update.zip) and no rom at all, nothing else.
The Recovery + Radio are from the Haykuro recent Rogers Heres your root thread . -> http://forum.xda-developers.com/showthread.php?t=544654
Oh well luckily your saved bro
Since you have the Cyan 1.4 recovery just boot up recovery go to console
then press enter
then enter this command ums_enable
Sd will mount to your comp
Shaquiel Harris said:
Oh well luckily your saved bro
Since you have the Cyan 1.4 recovery just boot up recovery go to console
then press enter
then enter this command ums_enable
Sd will mount to your comp
Click to expand...
Click to collapse
could you give me a breif walkthrough on how to short and sweet? i am really afraid to eff this up lol
and if this works, i will send you chocolate and flowers and ask you to marry me. maybe... lol
Edit: Also note i didn't do any backup type before this , i just have the update.zip from the spl, and think i wiped the data, im assuming once i get the sd card up all i need to do is stick the rom update.zip on there, then i can alt+s my way to a new rom, correct?
JsnLlnd said:
could you give me a breif walkthrough on how to short and sweet? i am really afraid to eff this up lol
and if this works, i will send you chocolate and flowers and ask you to marry me. maybe... lol
Click to expand...
Click to collapse
Maybe.. got my hopes up for nothing.. now i dont want to help.. xD
ok you have The Cyan 1.4 recovery installed right? and apparently your at fastboot after you have flashed the spl or whatever so press the end, menu and talk buttons to get out of fastboot. or just remove the battery doesent matter lol . But before you do that check the spl and make shure its 1.33.2005 to make shure your safe. once you turn the device back on hold the power and home button then recovery should come up. if you have cyan 1.4 recovery you should have a picture of the little android guy in the background lol and if so go all the way down until it says go to console. or just do alt+x. then once your in that screen then press enter once.
once you press enter the screen should have this up #
if so then just type ums_enable then press enter. it should look like this
# ums_enable
wait for a brief second and wallah your sd will mount to your comp. then flash whatever rom you had on before
Shaquiel Harris said:
Maybe.. got my hopes up for nothing.. now i dont want to help.. xD
ok you have The Cyan 1.4 recovery installed right? and apparently your at fastboot after you have flashed the spl or whatever so press the end, menu and talk buttons to get out of fastboot. or just remove the battery doesent matter lol . But before you do that check the spl and make shure its 1.33.2005 to make shure your safe. once you turn the device back on hold the power and home button then recovery should come up. if you have cyan 1.4 recovery you should have a picture of the little android guy in the background lol and if so go all the way down until it says go to console. or just do alt+x. then once your in that screen then press enter once.
once you press enter the screen should have this up #
if so then just type ums_enable then press enter. it should look like this
# ums_enable
wait for a brief second and wallah your sd will mount to your comp. then flash whatever rom you had on before
Click to expand...
Click to collapse
YES!!!!!!!!!!!! omfg thank you SO much for all of your help!!! Gonna slap a rom on that badboy now! woooooooo hahaha man i am jumping for joy right now, again Thank you!!
Now just to be sure im not screwing my chances up here, i remove the spl update.zip file and replace with the update.zip rom file?
JsnLlnd said:
YES!!!!!!!!!!!! omfg thank you SO much for all of your help!!! Gonna slap a rom on that badboy now! woooooooo hahaha man i am jumping for joy right now, again Thank you!!
Click to expand...
Click to collapse
xDDDD Its cool bro dont worry about it
JsnLlnd said:
Now just to be sure im not screwing my chances up here, i remove the spl update.zip file and replace with the update.zip rom file?
Click to expand...
Click to collapse
bro with that recovery you dont have to even rename it to update.zip anymore. just drag it to your sd then use the apply any .zip but you can if you want doesent matter
Did it work?
I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!
so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
help please!
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!
i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!
cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.
i dont have it plugged in when i use the terminal on the phone
cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.
It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App
yep make sure everything that has a capitals in it i capitalized in the terminal
this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.
i still can't figure out how to install a custom rom.
Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™
Hey !
I am new to the phone and I am so stupid...I formatted my intern SD Card with CWM Recovery..
So what can I do now?? Nothing is on the phone any more..cant flash anything..
Help me please!!
so_ony said:
Hey !
I am new to the phone and I am so stupid...I formatted my intern SD Card with CWM Recovery..
So what can I do now?? Nothing is on the phone any more..cant flash anything..
Help me please!!
Click to expand...
Click to collapse
Do you have s-off ? have you tried a RUU ?
so_ony said:
Hey !
I am new to the phone and I am so stupid...I formatted my intern SD Card with CWM Recovery..
So what can I do now?? Nothing is on the phone any more..cant flash anything..
Help me please!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2325853 - it's a sticky at the top of the Q&A page, it happens all the time, don't panic...
"just calm the fu** down", that is what I said to myself when it happened to me, because i panicked a little too...
you should follow the guide in the link that redbull123 provide
but if your fear is taking over you, there are two other and "for me" easily ways to install a rom if you fuc*... wiped your internal sd
1 - install HTC drivers as the provided link (above), then use DROID EXPLORER (look for it in google and install it) to copy a rom into your ONE, then flash!!!
2 - get a OTG cable copy the rom into usb and flash the rom using the usb memory with the OTG cable.
I remembere when i wiped my internal SD, it was because a skin for the recovery TWRP that changes the buttons, so I accidentally deleted my internal SD lol
redbull123 said:
http://forum.xda-developers.com/showthread.php?t=2325853 - it's a sticky at the top of the Q&A page, it happens all the time, don't panic...
Click to expand...
Click to collapse
i did it like there, the problem is, that i do not know where i have to go exactly with "cmd" mode...
I have the newest HBOOT 1.44.0000 so no RUU for this i think
i started the adb push but i only can go into recovery of TWRP . And what i have to do now?
i typed in adb push *rom* data/media/
but it says :"failed to copy rom to "data/media/ : is a directory
what does this mean?
so_ony said:
i did it like there, the problem is, that i do not know where i have to go exactly with "cmd" mode...
I have the newest HBOOT 1.44.0000 so no RUU for this i think
i started the adb push but i only can go into recovery of TWRP . And what i have to do now?
i typed in adb push *rom* data/media/
but it says :"failed to copy rom to "data/media/ : is a directory
what does this mean?
Click to expand...
Click to collapse
don't worry about hboot.
try selecting Advanced -> ADB Sideload in TWRP then in cmd command
adb sideload name_of_your_rom.zip
(make sure the rom is in the same folder as your adb/fastboot drivers and your running the cmd window from that folder also)
Hold shift and right click on your folder then click 'Open Command Window here' before you command anything.
redbull123 said:
don't worry about hboot.
try selecting Advanced -> ADB Sideload in TWRP then in cmd command
adb sideload name_of_your_rom.zip
(make sure the rom is in the same folder as your adb/fastboot drivers and your running the cmd window from that folder also)
Hold shift and right click on your folder then click 'Open Command Window here' before you command anything.
Click to expand...
Click to collapse
i did adb sideload but comming this failiure :ADB Sideload Complete -Failed-
so_ony said:
i did adb sideload but comming this failiure :ADB Sideload Complete -Failed-
Click to expand...
Click to collapse
Strange, I'd stay and try to help but I'm working in the morning so
make sure you have up to date drivers installed, maybe someone else can help...
good luck :good:
so_ony said:
i did adb sideload but comming this failiure :ADB Sideload Complete -Failed-
Click to expand...
Click to collapse
Does adb recognize your fone?
Cmd: "adb devices" it should display your fone, while being in recovery.
If not, try and flash latest twrp again, due to fastboot.
Sideload worked fine for me, as I formatted my sdcard..
Greetz MaW
Sent from my HTC One
Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?
KareemWaheed said:
Hey
My phone is LG L90 410
I was trying to install cm 12.1 -i'm on official lg lolipop rom-
first i tried to install CWM .. i used Flashify
then after try enter the recovery menu it says "secure booting error cause boot certification"
then enter a purple screen asking for something like RAM dump
any help please to fix this ?
Click to expand...
Click to collapse
Did you unlock the bootloader before install the recovery?
Can you still boot to android?
same problem here too... device is rooted ... tried to install twrp but when I want to enter into recovery this problem appears
Yes, in my case I can boot into android ... just when pink screen ram dump appears need to hold power button to restart and it boot android like normal
@KareemWaheed @gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.
neverdies said:
@gjurosi
Follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
This should fix your phones.
Click to expand...
Click to collapse
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user
gjurosi said:
tried but nothing,extract aboot.bin to external storage and in terminal when I tried to tipe commands it says unallowed user
Click to expand...
Click to collapse
Did you grant root permision, after typing "su" in terminal?
neverdies said:
Did you grant root permision, after typing "su" in terminal?
Click to expand...
Click to collapse
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone
gjurosi said:
last time I had that option ... now this situation,dont know anymore why I cant ...? I'll make factory reset then everything from the begining ... one question..when I downloaded this aboot.bin with unlock bootloader,I only need to extract it on external storage?
I cant see any (original) aboot.bin in external storage when I enter phone
Click to expand...
Click to collapse
As you can see at that guide, you need to put the patched aboot.bin on your external sd (/storage/external_SD/aboot.bin) then run the following commands on your phone's terminal.
Code:
su
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
After the su command you've to accept the root request.
Be sure to download and flash the right version of aboot for your phone variant, a wrong version of aboot will brick your phone.
@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying
gjurosi said:
@neverdies ....
in terminal I run the following commands ,but it says "cannot open for read:no such file or directory" ... I put aboot.bin on external storage ...dont know anymore wtf ?!? and I cant do factory reset !!!! again its security boot error and pink screen...
dont know why now... really annoying
Click to expand...
Click to collapse
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot
neverdies said:
Are you sure that your aboot.bin file is in /storage/external_SD?
You can put the aboot.bin in your internal memory instead, or anywhere else, just change command according to your aboot.bin file location.
Exemple if you put your aboot.bin file in /storage/internal_SD run the following command:
Code:
su
dd if=[B]/storage/internal_SD/aboot.bin[/B] of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
finally , it work ... aboot.bin were on external_sd ..but I dont know why the first time it didnt work ... I tryed again and it worked
flashed rom and everything now works ... thnxxx for help me solving the problem :good: