My device is GT-i9500 and it have 11G storage space by flash a pit file.
So, If I want to flash others stock firmware, I should adjust size of system.img from 2760m to 2150m.
I did it, and flash it successful with stock boot.img.But question comes here: DEVICE CAN NOT BOOT UP, it just stop at samsung logo.
then I flashed a custom kernel named Perseus, it BOOT UP!!!
I do not know the reason why it can boot and stock not.
If anyone know, please tell me.
What the question is: If it possible, how to make boot.img to boot my device?
My english is not good, hope you guys can understand!
big THANKS!!
Related
Hello, i did something wrong while trying to flash an ics custom rom on my vibrant phone, before to flash the ics rom i had an old froyo with android 2.2 with the old bootloader, i didn't notice that to flash the ics i had to first update to cm7 than update the bootloader and finally flash the ics rom. So, after flashed the ics the phone got stuck in the boot sequence and i had the bad idea to restore back the old froyo rom but i ended up to a totaly useless device, it doesn't boot anymore and stays stuck on the vibrant boot logo.
Please has anyone any idea if i can get out of this situation and flash back the original rom or at least any rom that works? I also can't reach the recovery menu anymore, i don't really know what to do! I Hope for someone can help me!
Thank You!
You can use Odin to restore it to stock, download the pit and tar file from here and flash it with Odin while the phone is in download mode: forum.xda-developers.com/showthread.php?t=1319802
Then use these steps to root and cwm: http://forum.xda-developers.com/showthread.php?t=849028
Thank you so much bro, it worked like a charm!!!
Cheers
You should check out my guide on how to install ics. Has all the steps and some that the video missed.
Also you need to take care when restoring as GB and ICS roms are partitioned differently therefore restoring something like the /data portion of your nandroid will cause 9 kinds or hell for you. And don't even get me going about the one full/fool proof way to brick your phone-the bootloader mismatch.
I am currently new to all this stuff so i dont have an exact idea what i was doing
First of all i rooted my Device I9500 Which had 5.0.1 Android
then i installed TWRP Recovery and then i was not able to backup any stuff to External SD Card so i installed some Boot.img which i exactly dont remember which i installed from watching any youtube video then later some problem occured It showed some error like "firmware upgrade encountered an issue" then i flashed Philz touch recovery which then worked and i was able to backup my data but i was not able to Boot into my Original ROM or couldnt see an option for that. Then i downloaded The Ozcan V6.3 ROM and tried installing it it succesfully installed but after that its not able to boot uo and stuck at SAMSUNG Logo Screen.
Please Help me What to DO !!!.
Thanks In Advance
If your device can still get into download mode, download the stock Android 5.x image for your device and flash it using Odin. That will get you back to square one so you can start over with rooting and installing the custom ROM.
I had the same problem on my gs4. It would only go to galaxy logo so I flashed the lollipop firmware via odin and all is well.
Sent from my GT-I9505 using XDA Free mobile app
Just have to flash the default one with Odin ?
i also backed up my old data with philz to my sd card that also and i also downloaded a new Default 5.0.1 ROM ?
Which one should i flash ?
and whats the critera for finding ROMs leaving the model number ? (noob question)
Is the S4 unlocked? If not, what country are you in and what carrier do you have?
My Country is India and its the International Version I9500 and i am not pretty sure that it was unlocked or not .but it was rooted and recovery was installed
Added later :
I just installed recovery back and then tried to install ROM the ROM was also stuck on the Boot Loop I think my boot loader isnt unlocked and ima stuck there because of that
I9500 isnt bootloader locked. And u must be flashing the boot.img on other partition that not in the odin package. So u must search how to repartition ur device. But. U MUST VERY CAREFULL WITH REPARTITION OPTION! U MIGHT BRICK UR DEVICE IF U DONT UNDERSTAND WHAT U DOING!. And if u wanna flash recovery and boot.img or bootloader thing. U must ONLY flash for I9500 version!. And if u successfully repartition ur device. U will lose all internal storage too. Ok good luck
Utkarsh_Chaudhary said:
My Country is India and its the International Version I9500 and i am not pretty sure that it was unlocked or not .but it was rooted and recovery was installed.
Click to expand...
Click to collapse
You would know if you were carrier unlocked as you'd be able to put a SIM from a different carrier into the S4 and have the device work. To get you the correct ROM we still need to know your carrier.
secure download : enabled
Hi my galaxy s4 gt i9500 is stuck in a bootloop. When is boot I get "firmware upgrade encountered an issue. Please select recovery mode in kies and try again"... when I boot into download mode I see "secure download : enabled" which wasn't usually there. Am trying to flash the pit file with twrp but Odin is failing.... is it because of the secure download enabled?? Please help me
You can't flash the PIT file with TWRP.
Do you have Odin? Do you have a copy of your stock ROM, downloaded either from Sammobile or samsung updates? If not, you'll need to get them. You then flash the firmware through Odin WITHOUT the PIT file. This should restore your device to operating condition. Afterward, you will of course need to root the S4 and flash a copy of TWRP to be able to install a custom ROM.
Carrier is Airtel
Have S5 SM-G900F - 16GB with PhilZ Touch 6.26.2 and Clockworkmod V6.0.4.7
Was using XtreStoLite_ROM_v2.2_LP_XXU1BOD3 and Blaze.Kernel_ver15 that I installed through SD card and Recovery.
As my S7 has shipped (finally) I want the GF to have my old S5 but need THL (Thailand) system support (I.E. not just thai language but also on the system menus).
I downloaded what I thought was a ROM for this but at the end of Odin flash I had Bad EXT4 flash and on phone 'invalid ext image size is too big'
Reading through the thread someone stated you need the .PIT.
I have ALWAYS avoided these but tried the SM-G900F_pit_16GB file. Yes I need a slap, I know better.....
OK so here it is, I do not know if NAND is corrupt as I do not know the symptoms.
Also, if I only have a soft brick, what is the best approach for recovery / ROM flash ?
Do I always need to do it from SD card / Recovery using a .zip?
Current state of phone.
Seen in Odin.
Can go into download mode.
Can now go into Recovery mode after flashing philz_touch_6.26.2-klte.tar.md5 in Odin.
Reboot loop (obviously, not valid ROM on it now).
I am assuming all is good and it's not a BAD brick, but still have not had a successful flash.
Many thanks
Yes I don't have many posts because I have always searched and found answers, but this time I am a little unsure and don't want to royally screw it up.
Help is much appreciated.
FizzerUK said:
Have S5 SM-G900F - 16GB with PhilZ Touch 6.26.2 and Clockworkmod V6.0.4.7
Was using XtreStoLite_ROM_v2.2_LP_XXU1BOD3 and Blaze.Kernel_ver15 that I installed through SD card and Recovery.
As my S7 has shipped (finally) I want the GF to have my old S5 but need THL (Thailand) system support (I.E. not just thai language but also on the system menus).
I downloaded what I thought was a ROM for this but at the end of Odin flash I had Bad EXT4 flash and on phone 'invalid ext image size is too big'
Reading through the thread someone stated you need the .PIT.
I have ALWAYS avoided these but tried the SM-G900F_pit_16GB file. Yes I need a slap, I know better.....
OK so here it is, I do not know if NAND is corrupt as I do not know the symptoms.
Also, if I only have a soft brick, what is the best approach for recovery / ROM flash ?
Do I always need to do it from SD card / Recovery using a .zip?
Current state of phone.
Seen in Odin.
Can go into download mode.
Can now go into Recovery mode after flashing philz_touch_6.26.2-klte.tar.md5 in Odin.
Reboot loop (obviously, not valid ROM on it now).
I am assuming all is good and it's not a BAD brick, but still have not had a successful flash.
Many thanks
Yes I don't have many posts because I have always searched and found answers, but this time I am a little unsure and don't want to royally screw it up.
Help is much appreciated.
Click to expand...
Click to collapse
Have you tried to flash a stock rom from sammobile ?
Soufiansky said:
Have you tried to flash a stock rom from sammobile ?
Click to expand...
Click to collapse
Yeah!
I tried various and get EXT4 file size incorrect errors.
It was the .PIT incident that was lead from that error.
I have since re-acquired the original de-oxed ROM and flashed that from .zip on SDcard.
All good now, I just thank god I didn't screw it up with a .PIT file.
I was lucky! Leave them files for the DEV's and ignore posts that suggest getting a .PIT file and trying that for .EXT4 partition errors.
Reading posts later, chances are that your getting that error because you have the wrong ROM to flash, having a hidden partition in the ROM, from someone like the UK EE provider.
Hope you remembered to disable reactivation lock during first boot
The reason the ROM was removed in the first place...
I went to install a custom OS for the very first time. I rooted my device with KingRoot and tried installing custom recovery via Flashify and i used a image file to flash the device and now when i boot the device it comes up with Samsung logo and then a blurred color screen and then blank screen. What should i do know... PLEASE SOMEONE HELP ME.
Two chances
1. You might have chosen boot image instead of recovery image option in flashify. boot image is kernel. device won't boot without kernel.
2. You have flashed wrong recovery image. you have to flash a working recovery image. make sure you downloaded right file.
Solutions
*If you have flashed Boot Image, then you have to download stock rom and flash it via Odin using a computer
*If you are flashed wrong recovery image then you can fix it by flashing right recovery.tar using odin
in both case you need a computer.
I suggest that you should go for an experts help.
You can find stock rom link and recovery.tar files at grand 2 general forum.
JitDevHacker said:
Two chances
1. You might have chosen boot image instead of recovery image option in flashify. boot image is kernel. device won't boot without kernel.
2. You have flashed wrong recovery image. you have to flash a working recovery image. make sure you downloaded right file.
Solutions
*If you have flashed Boot Image, then you have to download stock rom and flash it via Odin using a computer
*If you are flashed wrong recovery image then you can fix it by flashing right recovery.tar using odin
in both case you need a computer.
I suggest that you should go for an experts help.
You can find stock rom link and recovery.tar files at grand 2 general forum.
Click to expand...
Click to collapse
Thank you for your response. I installed the stock ROM using ODIN. And now, my phone is doing well. Fortunately, I upgraded from Jelly Bean to Kitkat. xD
Hi Everyone,
So My Samsung Tab A 2016 wifi only T580, is literally dead, but not physically, so the problem is exactly the same as Saznat is this thread: https://forum.xda-developers.com/galaxy-tab-a/help/samsung-t580-update-failed-frp-locked-t3914729
My tab is like new not a single scratch on it :crying:
the tab is:
running android 8
frp locked
can't boot into recovery no matter what stock rom I flash, all I get is no command
I can't flash twrp, the tab won't allow it because of frp lock.
any new tricks to try to fix it from the experts will be appreciated
Anyone??
Leboboy19 said:
Anyone??
Click to expand...
Click to collapse
Hello @Leboboy19 ,
Can you try using Odin (newest version ) and flash the original stock rom that you had before messing around with custom rom. make sure to uncheck re-partition. you may have to flash the stock boot and stock recovery .img which you will find on shellbox firmwares.
If that does not work can you try flashing the twrp md5 for that device . let me know
Bertonumber1 said:
Hello @Leboboy19 ,
Can you try using Odin (newest version ) and flash the original stock rom that you had before messing around with custom rom. make sure to uncheck re-partition. you may have to flash the stock boot and stock recovery .img which you will find on shellbox firmwares.
If that does not work can you try flashing the twrp md5 for that device . let me know
Click to expand...
Click to collapse
Thanks for your message brother, you reminded me of the tab after giving up on it, after months of trying finally found a fix.
to anyone having this problem:
1. Download your latest stock
2. extract it and swap the recovery.img with a recovery.img from a combination file that matches your binary number
3. Enjoy Your Recovered Tablet or sell it like me:laugh: