Related
I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob
Describe steps you have taken to root in detail.
i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob
any one can help me?
Vbob
Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...
vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot
[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?
hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, (i selected option 1 intall in /boot, i assume this is where i screwed up) this too went fine. but i couldn't install the new rom as it was no longer there, and now i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.
SemnteX said:
hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, this too went fine. but i couldn't install the new rom as it was no longer there, and no i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.
Click to expand...
Click to collapse
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy
simms22 said:
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy
Click to expand...
Click to collapse
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium
marty331 said:
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
yes i do, but i get confused using those, which is why i used the toolkit to unlock and root my device. unfortunately i got a little carried away and installed cwm into the wrong directory and overwrote the boot img.
SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.
simms22 said:
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.
Click to expand...
Click to collapse
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up
SemnteX said:
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up
Click to expand...
Click to collapse
No sir, how about reading this link!
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm sure there is something similar on xda but I have this link handy.
Sent from my Nexus 7 using xda premium
Changing the title of this post to problem solved doesn't help anybody in the future with a similar problem
Sent from my Nexus 7
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
Hi, I am very new and I really need some help I was trying to install a custom rom but something went wrong.
Waht I did was.
I first rooted my device,
then I installed the second bootloader TWRP
And I forgot the wifi on, so thw kindle fire HD updated itself and eliminate the super user app.
So I restored the kindle fire hd to ist default in the restore option in the main manu.
then I root it again,
and try to instal the second boot loader again,
but after I installed the second boot loader it never boots up into the kindle fire hd system,
what happends is, in turns on, appears the kinfle fire letter in orange, the aperars kinfle fire letters is blue, then kinfle fire letters in orange again, whit a animation, that use to appear when is about lo load the system, then it reboots itself and repeate the entire process but this time goes into the TWRP second boot loader.
I think I could fix it by just using the backuo files I made o I coul install the custom room I want from there, but the problem is that I cannot load any file to the kindle fire hd because when I connect it the pc it shows as ADB device. Please help me out with this. I would like to you help to restore it to stock or tell how can I transfer files to my kindle fire hd when is in TWRP mode.
I already tried the mount option on the TWRP but the pc does not recognized it as a portabla device where I can store files.
:crying::crying::crying::crying:
I think this is what happens when flash the old freedom boot image on the latest updates, not positive though. Anyways what kind of backups did you make, like a nandroid backup from twrp that u moved to Ur PC, or a backup as described in the fire flash tutorial made using adb? If its the adb method its really simple, you just boot into twrp and hit restart and then hit boot loader, it will go into fastboot where you can flash those images. Otherwise I suggest just downloading the latest prerooted amazon ROM in the android development section and trying to use the side load feature. I'll explain more after you post back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It happened to me this weekend, i messed up with my kindle, the solution was to use Kindle Fire HD and 2 First Aide Software http://forum.xda-developers.com/showthread.php?t=2096888
Hope it will help you
Nb: if the driver are not working use the one included in this post Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838
I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .
---------- Post added at 02:59 AM ---------- Previous post was at 02:54 AM ----------
abbashaider said:
I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .
Click to expand...
Click to collapse
stunts513 said:
I think this is what happens when flash the old freedom boot image on the latest updates, not positive though. Anyways what kind of backups did you make, like a nandroid backup from twrp that u moved to Ur PC, or a backup as described in the fire flash tutorial made using adb? If its the adb method its really simple, you just boot into twrp and hit restart and then hit boot loader, it will go into fastboot where you can flash those images. Otherwise I suggest just downloading the latest prerooted amazon ROM in the android development section and trying to use the side load feature. I'll explain more after you post back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .
So can you get into twrp or you mean you only have fastboot access? If you only have fastboot access you just need to make sure that you have installed the driver for the device (use the one in my signature if you haven't) and just use kindle fire first aid to restore the system.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
similar trouble - stuck with blue logo
I hope that this is the right thread for my problem. I've also tried to install a custom ROM on my KFHD 7'' - I did it using this guide: http://forum.xda-developers.com/showthread.php?t=2271909
I'm able to get into TWRP, wiped and I flashed the latest CM 10.2 from hashcode + the gapps but when I try to reboot the Kindle (after wiping again) it goes into orange logo, which changes to blue logo and stays there. I've waited for a long time and nothing changes - tried to advanced wipe all the stuff from my tablet and flash again, but I always end up on the blue logo. Also does not matter if I only flash the CM 10.2 alone without gapps.
Does anyone have any idea how I can progress from here? I should be able to restore my backups via Factory Cable - but this is not what I would like to do.
Thanks in Advance!
Gildoniel
So did you factory reset when doing this? And are you sure you grabbed the version of the ROM for your kindle?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
So did you factory reset when doing this? And are you sure you grabbed the version of the ROM for your kindle?
Click to expand...
Click to collapse
I did a factory reset, yes. And I took the ROMs from Hashcode for version Kindle Fire HD 7'' (my tablet) I managed to successfully flash CM 11 now -> I checked zip verification when installing the ROM, this seems to have helped. It is booting after a few seconds now.
Did not realize, that the zip verification was important (this was the only difference afaik) and now it seems to work smoothly.
All in all I am still a bit puzzled - but at least my tablet is up and running again.
I reckon the problem was caused by using the wrong boot partition image.
So as your KFHD had updated to v7.4.6 you would need to flash the
kfhd7-freedom-boot-7.4.6.img instead of the kfhd7-freedom-boot-7.2.3.img
Using the instructions from Hashcode's thread on installing a second bootloader and TWRP
Here: http://forum.xda-developers.com/showthread.php?t=2128848
I had the same problem and solved it by flashing the matching the correct Boot Image. I had Kindle v7.4.6 installed and used 7.2.3 Boot Image
Hope this helps,
Phill
Sent from my Amazon Kindle Fire HD using XDA Premium HD app
Same Problem, can't fix
Hi,
could you please let me know how did you flashed and replaced boot image...?
I have same problem and I can't do anything...
pls help me...
Thank you
shibli_xda said:
Hi,
could you please let me know how did you flashed and replaced boot image...?
I have same problem and I can't do anything...
pls help me...
Thank you
Click to expand...
Click to collapse
hurrah... I've fixed this problem in fastboot mood with my regular usb cable by the code below in cmd:
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
special thanks to hashcode for this tutorial:
http://forum.xda-developers.com/showthread.php?t=2128848
Hi,
First of all, my device info:
LeEco LePro 3 x727 on the 19s firmware.
I was following the guide found here: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560 to flash recovery and root my phone. Didnt realize it was for the x720 and not the x727 (stupid, I know)
Did everything in there, booted into the TWRP recovery, flashed the root file and rebooted.
Phone turns on, logo appears then shuts down.
I can't boot anymore.
I CAN boot into fastboot mode.
PC doesn't recognize my device
TWRP's sideload feature doesnt work
I'm obviously new at this, so I can't figure out a way to flash the firmware again (I guess that's what I have to do, do not know though).
What can I do?
I now flashed the correct TWRP file for my phone. works fine.
But how do I push files to the phone so I can flash them?
Any help would be greatly appreciated. Thanks!
Edit 1: Found this guide https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Should I follow that and see if it works? Will wait for confirmation first. Not gonna rush into it like the first time.
Thanks!
Yes here link to files you will need.
Qfil Look :
https://mega.nz/#!BJ52CApB!8lFCesul...r&utm_medium=referral&utm_source=DonanimHaber
Sent from my LEX727 using xda premium
mchlbenner said:
Yes here link to files you will need.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
So I should follow the guide and use those files? Any warnings or tips about the process? And also, no other way around that problem?
Thanks!
I have never needed to do this follow the directions to the tee.
It shame that fastboot doest work for you.
Sent from my LEX727 using xda premium
mchlbenner said:
I have never needed to do this follow the directions to the tee.
It shame that fastboot doest work for you.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
It actually works (fastboot I mean), but now I'm at the point where I try to sideload files but at 48% it gives me an error.
I had the same troubles, many wipes and try finally it worked... The stock file is the hardest to send, because the weight is so high.
marik1 said:
I had the same troubles, many wipes and try finally it worked... The stock file is the hardest to send, because the weight is so high.
Click to expand...
Click to collapse
I was able to push the files using adb instead of adb sideload.
Pushed the Lineage OS and now I'm currently running that.
Thanks for the help !
sirmamay said:
I was able to push the files using adb instead of adb sideload.
Pushed the Lineage OS and now I'm currently running that.
Thanks for the help !
Click to expand...
Click to collapse
If you had adb work why did not flash rwrp?
Sent from my LEX727 using xda premium
mchlbenner said:
If you had adb work why did not flash rwrp?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hmm, I did, maybe you missed it in the OP. I just wasnt able to push the files for some reason, had to flush the port (5037) to get it to work, and tried a lot of different adb versions until I got it to work with the mfastboot version of it.
Anyways, it's good to know there's another option in case I really brick it.
Thanks!
sirmamay said:
Hmm, I did, maybe you missed it in the OP. I just wasnt able to push the files for some reason, had to flush the port (5037) to get it to work, and tried a lot of different adb versions until I got it to work with the mfastboot version of it.
Anyways, it's good to know there's another option in case I really brick it.
Thanks!
Click to expand...
Click to collapse
Okay so in the original post you said that you do have twrp installed, and you can boot into twrp recovery...right.
Go buy an OTG drive
Load your Rom, Gapps, and Magisk onto otg flash drive
In TWRP: Go to "Wipe" and then to "Advanced Wipe" (Check: Dalvik / ART Cache, System, Data, and Cache
Swipe to Wipe > then go to main menu. ( Note, if you get a Encryption message you will have to wipe the storage, as long as Twrp recovery is installed there will be no issues)
Go to Install then select OTG : Select the ROM file then click "Add more Zips" and select the Gapps and Magisk files
Swipe to confirm Flash
Reboot to system