So i have been attempting to root a friends hero and i have mixed luck. First of i had a terrible time trying to root. I used regaw's tool to attempt root at first only to find that it did not stick and not provide root. after successfully getting stuck at the htc screen as a result I was forced to use the stock ruu to get the phone running again. (2.31.651.7) After about an hour of reflashing (eventually using the sd card method) I used the rageagainstthecage exploit (non superoneclick method) and this successfully worked. after this i obtained Soff using regaw Soff method. after SOFF was sucessfully achieved I drank a beer sighed, and used ROM Manger to flash recover.....This is where the trouble starts.
It took 2 flashes of clockwork to stick. I thought of using RA but I am not familiar with RA at all. I downloaded the latest version of Cyanogen (rc 7 something) and did a NAND backup before proceeding. After doing a Full wipe I flashed Cyanogen + Gapps and everything looked good except now im stuck in the HTC screen. Ive tried everything and dont want to revert to stock in case ive forgotten something. Any direction would be helpful! Thanks in advanced!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This shows my hboot version +settings
This is what im looking at now
try pressing volume up and fastboot usb then run the ruu again i had to do that after a radio failed to install you wont be rooted unfortunately but you can place a rooted rom in the hercimg and go from there.
Do i need to tweak the rom at all? I picked (i think) nfx stock rooted rom. Do you have a suggestion as to which rom to pick?
Also can you flash anything from HBoot or fastboot? If its hard to explain feel free to link!
u can flash roms radios and splash screens from hboot but its not for the faint of heart i still would do it through recovery once u have it installed. as far as roms go if you want android 2.3 i would go with hero deck its the most stable in my opinion everyone will think different though. and as far as 2.1 sense roms i would deffintly pick nfx stock. i suggest reading through the threads il duce put up at the top of the q/a section some of that info will probably save your phone more than once.
After doing what you said Im back in android with a working phone Thank you again!
no problem.
Well I thought this was over but apperently not. I cannot use anything but the stock rooted roms.....Nothing else will flash cept that. I tried renaming the cm7 zip to hercimg.zip but it still didnt work. Got stuck in the htc boot screen again. What do you reccomend i do?
Did I miss a step somewhere along the way?
1.Rage exploit
2.Custom recovery
3. Regaw Soff Hboot
Also apps will not install.....says there is insufficient space.... don't know if that helps at all.
Attempted a 1 click root out of curiosity earlier forgot i screenshot the error
never rename roms, make sure you install your recovery then go to partitions and format boot,system,data,cache then go to advanced and wipe dalivk after that install cm7 or the rom of your choice then install gapps if needed
Still Stuck at white and green htc screen....heres what i did
Is that cant mount error a problem?
no thats not it the only other thing i can tell yea is try a different rom like hero deck you definitely did everything right the first boot should take about 5-10 minutes. or you could use aman ra and see if that helps.
oh and i just noticed that you wiped dalvik afterwords, your need to do it before installation
Just did everything still in clockwork but trying hero deck. Still locking up.....I think im going to try going back to stock and then re rooting.....im now getting a [140]Bootloader error when i try to use the stock RUU file. Is there any way since i have the S-off Hboot to make it accept an older ruu? I have a 2.31.651.5 ruu which would make re rooting suck less and i think coming from .7 may have cause this set of events.
Same Problem after a revision to stock anything else i can do? I still have s off and as soon as i revert again Ill have root?
If you have adb try reflashing your recovery threw adb. Also format your sd threw your pc and return the stock default then format it your recovery after you reflash it. No partitions no swap just all system / fat. Then redownload the rom and gapps then flash the rom then the gapps to see if it boots up. Remember backup all of the data on your sd first. Hope this helps. And I'd recommended Ra.1.7 or cwm2.5
Locked & Loaded
It didnt go for it ......im gunna leave it s off and give him root and call it a day
TheShackSpecialist said:
So i have been attempting to root a friends hero and i have mixed luck. First of i had a terrible time trying to root. I used regaw's tool to attempt root at first only to find that it did not stick and not provide root. after successfully getting stuck at the htc screen as a result I was forced to use the stock ruu to get the phone running again. (2.31.651.7) After about an hour of reflashing (eventually using the sd card method) I used the rageagainstthecage exploit (non superoneclick method) and this successfully worked. after this i obtained Soff using regaw Soff method. after SOFF was sucessfully achieved I drank a beer sighed, and used ROM Manger to flash recover.....This is where the trouble starts.
It took 2 flashes of clockwork to stick. I thought of using RA but I am not familiar with RA at all. I downloaded the latest version of Cyanogen (rc 7 something) and did a NAND backup before proceeding. After doing a Full wipe I flashed Cyanogen + Gapps and everything looked good except now im stuck in the HTC screen. Ive tried everything and dont want to revert to stock in case ive forgotten something. Any direction would be helpful! Thanks in advanced!
This shows my hboot version +settings
This is what im looking at now
Click to expand...
Click to collapse
Try Flashing Just the Rom, then let it Boot, Then Reboot to Recovery and Flash the Gapps!
Good Luck!
Related
I'm a HTC guy here and we always just use recovery (Amon_Ra or Clockwork) to wipe data/system restore before flashing a new rom. We don't have to revert all the way back to completely stock. It seems to me that I should just be able to use the update.zip to install Clockwork recovery, do a full wipe, and flash a new rom.
If I'm already on the stock rom do I still need to ODIN before rooting/flashing or can I just root/flash? Every time I switch roms do I have to ODIN back to stock, re-root, then reflash? That sounds really obnoxious.
Just wondering if anyone can explain the difference to me because it's not making sense. I'm suddenly REALLY glad I have an HTC phone with T-mobile.
Thanks!
This confused me at first as well since I had a magic.
I think mainly it is because of the lagfixes and compatibility with some of the recovery modes. Instead of thinking whether this may be right or not, if you ODIN then flash a new rom, you get rid of potential problems compared to just the standard wipe. That's my take on it anyways and I just follow the majority.
Sent from my GT-I9000
don't blame me when your phone explodes but i've never flashed back to stock once i starting using custom ROMs. and i've flashed at least 10.
It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.
And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard
avgjoegeek said:
It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.
Click to expand...
Click to collapse
I agree, wiping is important and I always do it from recovery by choosing WIPE DATA/FACTORY RESET. My actual question is this:
Why not just use Clockwork Recovery to wipe? That's what I always did with my Magic 32B and what I've done so far with my Glacier. It has never caused me any trouble to do it this way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As for the sdcard and maintaining root - I'm really not sure how that's related, as root access is under /system, which doesn't live on the sdcard, right?
avgjoegeek said:
And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard
Click to expand...
Click to collapse
That's actually how I flashed Cog 2.3b8. From her stock setup just update.zip to clockwork recovery, wipe data/factory reset, flashed Cognition and went on with my life.
QUESTION - Updating to Cog 3 do I need to uninstall lagfix before flashing anything else? Can I flash Cog 3 over Cog 2 as an update.zip without wiping data? If I do wipe will a WIPE DATA/FACTORY RESET be sufficient or do I need to ODIN? If I use the wipe through clockwork do I need to uninstall lagix first?
Sorry for all the questions, I'm still learning how all of these things interact with each other.
you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.
mengbo said:
you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.
Click to expand...
Click to collapse
So add the disable lagfix folder, reboot, then go back to cwr, wipe data flash, cog3? I would really like to avoid wiping if possible, but oh well...
that is correct. copy the cog 3 install package to your phone internal sd, remove external sd and sim before update for safe by the way .
I have a flashing problem, I don't know how to explain very well, every time I try to flash a kernel/mod etc via recovery, it disapears after rebooting the system, it won't stick there! I tried to upgrade from thunderzap to siri via CWM, and it didn't upgrade.. So I made a fresh install, flashed JB via odin, everything was fine, but now I can't flash anything via recovery, not even the CWM recovery, It shows that it's successfully flashed, but it simply disappears after the first reboot, I need held really bad. I can't find something similar, it can be a hardware problem? I successfully flashed root, but can't do nothing more, it will not "stay" in my phone. Devs, what do you think I should try?
Одг: Flashing problems
Tekie said:
I have a flashing problem, I don't know how to explain very well, every time I try to flash a kernel/mod etc via recovery, it disapears after rebooting the system, it won't stick there! I tried to upgrade from thunderzap to siri via CWM, and it didn't upgrade.. So I made a fresh install, flashed JB via odin, everything was fine, but now I can't flash anything via recovery, not even the CWM recovery, It shows that it's successfully flashed, but it simply disappears after the first reboot, I need held really bad. I can't find something similar, it can be a hardware problem? I successfully flashed root, but can't do nothing more, it will not "stay" in my phone. Devs, what do you think I should try?
Click to expand...
Click to collapse
First, CWM can't be flashed via recovery and stay. That is temp CWM. You need to install kernel with integrated CWM. You need to unpack SIRI zip, to get CWM flashable instalation. You probabli just flashed zip that contains both kernels, dd, and CWN flashable. Did you get success message after instaling it?
Sent from Galaxy S Advance
If you don't know the DD commands you can also download Universal Kernel Flash Tool and flash using this simple APP.
All you need is to download the "kernel.bin.md5" you want to flash to your phone, load it with the app and press flash (explanation in the link).
Yeah, it is successfull! For example from stock recovery I flash the CWM update zip (the separate version, as in instructions). The recovery is now CWM, I can flash everything, it says successfull, but it doesen't "stay" in my phone after reboot. Should I asume is a hardware problem? Flashing via Odin is working, flashing root zip is working as well.
I also tried flashing siri RC3 (with CWM integrated) via Terminal Emulator, it worked, but the phone it's still broken, when I try to update to RC4 via recovery, or flash anything else, it is flashed, it shows that the installing was successfully but after reboot.. boom it isn't there
Tekie said:
Yeah, it is successfull! For example from stock recovery I flash the CWM update zip (the separate version, as in instructions). The recovery is now CWM, I can flash everything, it says successfull, but it doesen't "stay" in my phone after reboot. Should I asume is a hardware problem? Flashing via Odin is working, flashing root zip is working as well.
Click to expand...
Click to collapse
How did you flash CWM. You used that Temporary CWM. Like you do not listen to me. It is Temporary because it will not stay. You need to install kernel with CWM. Because it is on the same partition. SO YOU CAN'T INSTALL CWM WITHOUT KERNEL. IT WILL BE PERMANENT ONLY WHEN IT IS INSTALED INTEGRATED INSIDE OF KERNEL. Any of our JB custom kernels have permanent CWM.
It seems i'm not a too good explainer. Is there any way to make screenshots in recovery? I will show you step by step
I installed siri RC3 via terminal emulator, now I have permanent CWM, but I can't flash anything with it, even if it says the kernel is successfully upgraded, etc. I don;t know how to take screenshots in recovery, but I have those:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Installing siri RC3)
(The siri RC 3)
(the kernel after "successfully" flashed siri RC4 via CWM)
It seems I can't flash anything via recovery, stock or CWM it doesen't make a difference, but terminal emulator or odin are fine. Another mention: I know I am kinda noob, but i'm not retarded, I know hot to use recovery, it worked fine since today...
Tekie said:
I installed siri RC3 via terminal emulator, now I have permanent CWM, but I can't flash anything with it, even if it says the kernel is successfully upgraded, etc. I don;t know how to take screenshots in recovery, but I have those:
View attachment 1749221 (Installing siri RC3)
View attachment 1749222 (The siri RC 3)
View attachment 1749223 (the kernel after "successfully" flashed siri RC4 via CWM)
It seems I can't flash anything via recovery, stock or CWM it doesen't make a difference, but terminal emulator or odin are fine. Another mention: I know I am kinda noob, but i'm not retarded, I know hot to use recovery, it worked fine since today...
Click to expand...
Click to collapse
Hm, lets do one test. I will make you flashable zip with some application and you see if it is installed. Just to figure out what app to put in system.
P.S. No, do one thing. Backup your ROM in CWM. Then use Frapeti's CWM that deodex ROM. And see if all *.odex files are gone from system/app.
http://forum.xda-developers.com/showthread.php?t=2095301
Or try black status bar mod from there. If it is changed to black, that it is working normaly.
The status bar mod worked (I did it before deodex and it worked, so I think it doesn't require deodex.. doesn't matter)
I installed deodex zip, it worked.. So the problem is only when I flash kernles or mods that are .zip ... I think I will stick to stock with a kernel that doesn't require flashing and that's all.. if you can find an answer I will be very thankful anyway.
Одг: Flashing problems
Tekie said:
The status bar mod worked (I did it before deodex and it worked, so I think it doesn't require deodex.. doesn't matter)
I installed deodex zip, it worked.. So the problem is only when I flash kernles or mods that are .zip ... I think I will stick to stock with a kernel that doesn't require flashing and that's all.. if you can find an answer I will be very thankful anyway.
Click to expand...
Click to collapse
And what file did you use for kernel, post link to see is it CWM flashable. You can't just zip it and install.
Sent from Galaxy S Advance
shut_down said:
And what file did you use for kernel, post link to see is it CWM flashable. You can't just zip it and install.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
Siri kernel RC4 http://www.tusfiles.net/w043syx4a7hg
There are other things that "disappear" after flashing like moded lockscreen or moded sms. It will just not flsuh zips, I can't explain why terminal emulator is working, or why deodex.zip is installing.. I'm too tired to figure it out. Can you learn me another way to flash the RC4 kernel without recovery? thunderzap is a little choppy and siri RC3 has some vibrator bugs wich make it unusable for daily use.
Tekie said:
Siri kernel RC4 http://www.tusfiles.net/w043syx4a7hg
There are other things that "disappear" after flashing like moded lockscreen or moded sms. It will just not flsuh zips, I can't explain why terminal emulator is working, or why deodex.zip is installing.. I'm too tired to figure it out. Can you learn me another way to flash the RC4 kernel without recovery? thunderzap is a little choppy and siri RC3 has some vibrator bugs wich make it unusable for daily use.
Click to expand...
Click to collapse
You did unpack this zip and used I9070_CWM_FLASHABLE_SIRI_KERNEL_rc-4.zip? You should't flash I9070_SIRI_KERNEL_Rc-4_PACKAGE.zip. Because it contains CWM flashable zip, that you should flash, and kernel that should be flashed with DD command. It is a package, just for easy download.
And you can't flash ThunderZap from its official thread with CWM. It can be only instaled with DD command method.
For SMS you need to remove current secmms.apk to make new work. And to remove secmms.odex if you are not deodexed.
I think there is no problem with your instalations in CWM, just need to figure out how things work.
Thanks man, I totally forgot about that! I was so worried about the broken flashing thing that I forgot, thank you a lot, i will just flash with dd.
Tekie said:
Thanks man, I totally forgot about that! I was so worried about the broken flashing thing that I forgot, thank you a lot, i will just flash with dd.
Click to expand...
Click to collapse
You are welcome. And do not worry, everything is ok with your phone.
Hi. here is my situation: i had the phone unlocked and on stock 4.1 firmware, rooted.
Today i wanted to try kitkat and downloaded some Xperia V 4.4 Rom. after going into recovery i started the install but i failed somewhere in the middle.
Well, ended up accidentally backing out of CWM (i had a nandroid backup) without repairing the fone and now its stuck in a bootloop. its the fastest i've seen, the phone is on for line 2 seconds (on SONY logo) then reboots. i tried adb, fastboot, but these require (i think) some level of initialization that the phone just doesnt get into.
I tried PC Companion but it says it cannot repair the phone as custom firmware is detected. Can i force it to update even in this situation?
mechlord said:
Hi. here is my situation: i had the phone unlocked and on stock 4.1 firmware, rooted.
Today i wanted to try kitkat and downloaded some Xperia V 4.4 Rom. after going into recovery i started the install but i failed somewhere in the middle.
Well, ended up accidentally backing out of CWM (i had a nandroid backup) without repairing the fone and now its stuck in a bootloop. its the fastest i've seen, the phone is on for line 2 seconds (on SONY logo) then reboots. i tried adb, fastboot, but these require (i think) some level of initialization that the phone just doesnt get into.
I tried PC Companion but it says it cannot repair the phone as custom firmware is detected. Can i force it to update even in this situation?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use flashtool to flash a stock FTF
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
davidtkf88 said:
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
Click to expand...
Click to collapse
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
gregbradley said:
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
Click to expand...
Click to collapse
Then the only way is to enter fastboot mode and flash stock kernel
gregbradley said:
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
Click to expand...
Click to collapse
I did a nandroid backup, but it didnt use it. I backed out of cwm after the installation failed.. i cant get into CWM again because the LED doesnt light up. Like i said, the phone powers for like 2 seconds and then restarts.
I think the cwm i had was overwritten or is somehow unusable. i cant use any tool because the phone doesnt sat powered long enough for any tool to recognize it. i dont even think it initializes whatever it is initialized for adb and the rest
davidtkf88 said:
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
Click to expand...
Click to collapse
I did a nandroid backup, but it didnt use it. I backed out of cwm after the installation failed.. i cant get into CWM again because the LED doesnt light up. Like i said, the phone powers for like 2 seconds and then restarts.
I think the cwm i had was overwritten or is somehow unusable. i cant use any tool because the phone doesnt sat powered long enough for any tool to recognize it. i dont even think it initializes whatever it is initialized for adb and the rest
Flash a stock kernel, use doomkernel, enter Recovery and restore your backup
Leave it on charge for a few hours first
Sent from my C6903 using XDA Premium 4 mobile app
Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
vindikleuk said:
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Follow
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat and use PIT file, to repartition with the JVU 2.3.6
Check this out! Links to useful Guides and " Banned " Documentaries
vindikleuk said:
Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2
TeKnoGin said:
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Wow, how did I not think of that? Thanks!
I have a real issue trying to install any zip files for ROMS.
At first I thought it was just the file I had downloaded so I downloaded another, and another, and another through a different browser (as I had read this might be an issue?).
Still nothing worked. I've put some screenshots below of what I am getting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I flashed a newer version of CWM (from the Cyanogenmod thread) and got this...
These are all stored on my external SD card which is where I am trying to boot from. The weird thing is that I can install the Alliance ROM but no others! I'm not sure whether its something to do with the Alliance one being a 4.3 ROM and the others all based around 4.4??
I really am out of ideas and can't find any solutions that seem to work, please can anyone help?
User does not have CWM recovery in image one its stock 3e.
Image 2 reads as a faulty file package .
Please try Philz Recovery .
Thanks.
I'm not quite sure what you mean by your first sentence but I will try Philz Recovery as well.
I've just flashed Philz Recovery but still no joy
I tried installing CM and OmniRom which was stored on the phone, and then also from the SD card but its still giving me the same messages?
I really am at a loose end here, I'm hoping there is a simple explanation for this????
Simple explanation reads as faulty zip files .
message says cannot open .
First sentence you did not have a custom recovery only stock recovery on image one .
Suggest format phone in recovery format sdcard system data cache then boot to download mode and flash stock rom .
With 63 posts you can ask in your roms thread or its Q&A thread ,
I see that you installed Philz Touch 5. Try latest 6.12.8: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 > This is based on CM11 tree, so it will work only with ROMs that hve the update binary from a CM11 ROM. So it will work with the stock CM11 you are trying to use. Try before you flash the ZIP to search it with ES File Explorer. If it appears the files inside it, than it should be OK. If it shows an error message saying that it is not a ZIP, you hve to download it again, because the file is not good. You have here:http://forum.xda-developers.com/showthread.php?t=2201860 some other issues and how to fix them. Hope I helped you.
I have to agree, go back to full stock, the modify the phone step by step. Root-cwm-custom rom
Sent from my GT-I9305 using xda app-developers app
Thanks for your replies guys.
This is odd, but I now have CM11 on my S3 LTE.
After installing Philz Recovery, I then reverted back to the latest version of CWM and tried to re run the file and this time it ran! I have no idea what was going on there?
Just in case this whole thing happens again if I want to flash an alternative ROM... What are the steps for returning the phone to a factory 'stock' state?
zim_zimmer said:
Thanks for your replies guys.
This is odd, but I now have CM11 on my S3 LTE.
After installing Philz Recovery, I then reverted back to the latest version of CWM and tried to re run the file and this time it ran! I have no idea what was going on there?
Just in case this whole thing happens again if I want to flash an alternative ROM... What are the steps for returning the phone to a factory 'stock' state?
Click to expand...
Click to collapse
See the sticky in General .
All sorted now, thanks guys
Sent from my GT-I9305 using Tapatalk