Database Info

[Q] Please HELP ME

Hi Guys
I have an samsung galaxy sl gt-i9003 it had stock rom 2.3.6 ddlf2 ,after i tried to root it with CF-Root for most I9003 firmwares DDLF2_CFROOT-05-07-2012.tar (CWM 5.0.2.8) it flashed succesfully and my phone booted then i copied the RemICS-JB v3.1 File to memory card after i tried to flash the rom according to the instructions it went to an boot loop
then when i factory reseted many times no use the i tried to come back to stock rom ddlf2 after it completed it showed this error
E:format_volume:rfs format failed on /dev/block/stl10
somekind of that error

try to flash with odin 1.83

it's using MTD partition layout, first flash will format your phone partition and reboot itself.(based on CM10A4 instruction)
After that flash again with the same file, then flash gapps.

alex88510 said:
it's using MTD partition layout, first flash will format your phone partition and reboot itself.(based on CM10A4 instruction)
After that flash again with the same file, then flash gapps.
Click to expand...
Click to collapse
hi alex
to move to stock rom should i flash any latona.pit with firmware files in odin

karthik gowtham said:
hi alex
to move to stock rom should i flash any latona.pit with firmware files in odin
Click to expand...
Click to collapse
Flash pit file then the firmware files WITHOUT bootloader file.
Sent from my GT-I9003 using xda app-developers app

oh man i searched all the post about the above error and downloaded many file but the good thing is my phone boots up but the bad thing is it STUCK in a boot loop

karthik gowtham said:
oh man i searched all the post about the above error and downloaded many file but the good thing is my phone boots up but the bad thing is it STUCK in a boot loop
Click to expand...
Click to collapse
This could solve your problems
Go to Download Mode
Flash xxkpe leaving the boot loader blank through odin form pc
fill the rest
wait for complete installation
reboot in recovery
wipe everything
reboot in download mode
again flash xxkpe now with bootloader
after flashing completed wait for reboot
now reboot in download mode
flash ddlf2 via pda
wait for completion of flashing
reflash bam 15 cr 7 kernel
http://forum.xda-developers.com/showthread.php?t=1355675
let it reboot.
follow the instructions given below
http://forum.xda-developers.com/showthread.php?t=1869820&page=44
thats it.
if your internel memory is corrupted then you can try this as a last chance
because it is very precise
http://forum.xda-developers.com/showthread.php?t=1651619
I recommend you to visit the samsung service centre if your internel memory is corrupt
its in egmore
very near the railway station
or else pm me

My SGR can't start

Hello, friends!
I have a big problem with my Samsung Galaxy R, here is what happened:
I have used BlueBerry Rom V1 on Android 4.0.4 Kernel, but tried to install 4.2.2 Avatar ROM - zip via CWM. It shows me that everything is ok, reboot the phone and after that - I only see the Avatar screen but phone doesn't load. I load download mode and install new ROM via Odin, but the same thing happened - everything is ok, the ROM is installed successfully, I see the starting screen with Samsung logo, but that's all. It doesn't want to start - I wait, and wait, and nothing.
Here are some points that maybe are important:
- When I first install Android 4.0.4 Kernel I swap internal (4GB) with external SD (32GB) - my SD card become phone memory. After that many problems happened. I think that SD card I bought is not good quality and all the files I copy on the SD card (recognized as USB phone memory), won't open. For example when I make camera photos and save them to this card, I can't open them after that. When use the internal (4GB memory, recognized as 'external sd'), there is no problem.
- For this reason I copy the Avatar ROM .zip file both to external and internal sd card. So when I choose install from sd card (unlike the phone, CWM don't recognize the external 32 SD card as internal) - I choose the zip file, and immediately receive an error - bad file. So I was unable to install the Avatar ROM via CWM with the standard option "install zip from sdcard". I choose "install zip from internal memory" and then choose the zip file. As I said - everything was successful, until I realize that the phone doesn't want to load.
I am sorry for my bad English and hope you will understand my problem. I tried with Kies Firmware Emergency Firmware recovery, but it is said that I need recovery code.Also tried with Kies Firmware Upgrade & Installation, but nothing happened.
I really hope that here can find somebody who will help me. Thank you in advance!

deasly said:
I load download mode and install new ROM via Odin, but the same thing happened - everything is ok, the ROM is installed successfully, I see the starting screen with Samsung logo, but that's all. It doesn't want to start - I wait, and wait, and nothing.
Click to expand...
Click to collapse
At This Stage, You should enter into recovery mode (hope you know key combination) and do a factory reset.
Enter Download Mode->Flash Stock Ics via odin->enter into recovery->do Factory Reset It should boot then..
To Avoid Confusion, remove your 32Gb memory card and do flashing.
Hope it Helps..

Solved!
Nikhil said:
At This Stage, You should enter into recovery mode (hope you know key combination) and do a factory reset.
Enter Download Mode->Flash Stock Ics via odin->enter into recovery->do Factory Reset It should boot then..
To Avoid Confusion, remove your 32Gb memory card and do flashing.
Hope it Helps..
Click to expand...
Click to collapse
Many thanks!! ))))))

Nikhil said:
At This Stage, You should enter into recovery mode (hope you know key combination) and do a factory reset.
Enter Download Mode->Flash Stock Ics via odin->enter into recovery->do Factory Reset It should boot then..
Click to expand...
Click to collapse
This is not a good idea. Stock recovery and ICS both have brick bug in kernels.
Sent from my GT-I9103

Adam77Root said:
This is not a good idea. Stock recovery and ICS both have brick bug in kernels.
Click to expand...
Click to collapse
yes.both have brick bug in kernels.
whenever i installed stock ics via odin after installing custom rom, my phone entered into bootloop. it stuck to samsung logo.
since stock recovery doesnt come up with more options, only thing i could do was factory reset and it booted then, hence suggested.
Are following steps safe?
-flashing stock ics
-flashing cwm 4.0.0.2 via odin
-factory reset
-reboot
if not then, what is the safe solution?

Nikhil said:
yes.both have brick bug in kernels.
whenever i installed stock ics via odin after installing custom rom, my phone entered into bootloop. it stuck to samsung logo.
since stock recovery doesnt come up with more options, only thing i could do was factory reset and it booted then, hence suggested.
Are following steps safe?
-flashing stock ics
-flashing cwm 4.0.0.2 via odin
-factory reset
-reboot
if not then, what is the safe solution?
Click to expand...
Click to collapse
Flash ardatdat kernel after CWM & then do factory reset.

Disturbed™ said:
Flash ardatdat kernel after CWM & then do factory reset.
Click to expand...
Click to collapse
This! ^
Sent from my GT-I9103

Adam77Root said:
This! ^
Sent from my GT-I9103
Click to expand...
Click to collapse
What if this kernel doesnot exist on sdcard. AKAIK only way to flash this kernel is through recovery like CWM,philZ, (installing from sdcard).
when i faced this problem, i didnt have ardatdat's kernel zip file in sdcard.

Nikhil said:
What if this kernel doesnot exist on sdcard. AKAIK only way to flash this kernel is through recovery like CWM,philZ, (installing from sdcard).
when i faced this problem, i didnt have ardatdat's kernel zip file in sdcard.
Click to expand...
Click to collapse
You can push it using adb or mount USB storage and move it.

Tf101 Installing EOS stuck on "Installing update..."

Hi, i have Team EOS rom on my tf101 and it has been working without any problem. But today it stuck on EOS logo when boots. I enter on cwm (version 5.0.2.8) and do a wipe (factory settings / cache / dalvik and format /system) and try to install the EOS rom again but it stucks on "Installing update..." I have tried several times with the same result. I tried KatKiss 4.2.2_225 from sdcard with the same result.
Any help thanks.

anibol said:
Hi, i have Team EOS rom on my tf101 and it has been working without any problem. But today it stuck on EOS logo when boots. I enter on cwm (version 5.0.2.8) and do a wipe (factory settings / cache / dalvik and format /system) and try to install the EOS rom again but it stucks on "Installing update..." I have tried several times with the same result. I tried KatKiss 4.2.2_225 from sdcard with the same result.
Any help thanks.
Click to expand...
Click to collapse
I would HIGHLY recommend updating to TWRP.
If you can flash from the microSD, grab a flashable zip file like 2.6.1.0 from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
If not, you can push the TWRP zip file to the /sdcard/ using adb and flash that.
A last option is to use EasyFlasher to install it using APX mode. I have repacked easyflasher with newer recoveries here: http://forum.xda-developers.com/showpost.php?p=43986513&postcount=250
In my experience, many users have had big issues (myself included) trying to use CWM and anything beyond Android 4.1.X ROMs on the TF101. TWRP has far fewer issues and it can flash from both internal and external storage.

frederuco said:
I would HIGHLY recommend updating to TWRP.
If you can flash from the microSD, grab a flashable zip file like 2.6.1.0 from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
If not, you can push the TWRP zip file to the /sdcard/ using adb and flash that.
A last option is to use EasyFlasher to install it using APX mode. I have repacked easyflasher with newer recoveries here: http://forum.xda-developers.com/showpost.php?p=43986513&postcount=250
In my experience, many users have had big issues (myself included) trying to use CWM and anything beyond Android 4.1.X ROMs on the TF101. TWRP has far fewer issues and it can flash from both internal and external storage.
Click to expand...
Click to collapse
So the best way to do it is using EasyFlasher right?
What option should i use: Flash or Unbrik, and what recovery system do i select, TWRP? Thanks.

anibol said:
So the best way to do it is using EasyFlasher right?
What option should i use: Flash or Unbrik, and what recovery system do i select, TWRP? Thanks.
Click to expand...
Click to collapse
I would use the TWRP 2.6.0.0 repacked EasyFlasher and then just install recovery (select the TWRP 2.2.0 from the dropdown and it WILL install 2.6.0.0).
I have a detailed guide here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html

Hi Fred, thanks for you guides. I have following it and i have TWRP installed, i have booted in recovery mode and when i install EOS rom the progress bar remains stuck, move for 1 second , stuck again and move a bit again and i don't know if this is normal, how much time i have to wait....Any hint?
Thanks in advance

I forget it. When i did the wipe i get an "Unable to mount /system" Is this normal? May be i have not enough space for the update?

anibol said:
I forget it. When i did the wipe i get an "Unable to mount /system" Is this normal? May be i have not enough space for the update?
Click to expand...
Click to collapse
Hmmm....thats not good.
It could be that your internal storage has a personal issue. I would try using EasyFlasher to flash back to stock. Just download the update from Asus, put it in the "asusupdate" folder of EasyFlasher. Do not unzip the file at all.
Instead of installing TWRP, flash stock. See if that boots.
If it does, then flash TWRP again and see if you get the same system error.

Not booting to recovery

what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
EDIT (FIXED)
WHAT WENT WRONG...
1. Was using CWM (When i was last active in android flashing, twrp was just another custom recovery, cwm was needed for cm)
2. When i did use TWRP, it was an older version, and did not work (did not even boot to recover, in fact)
3. When i did get twrp working, i used a bad cm.zip file (corrupted)

nishant_713 said:
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
Click to expand...
Click to collapse
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended

bloodhound42 said:
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
Click to expand...
Click to collapse
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)

nishant_713 said:
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
Click to expand...
Click to collapse
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know

bloodhound42 said:
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
Click to expand...
Click to collapse
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Update -- Ok flashed 2.8.6.0 and now boots to revovery (even after a restart) but still can't flash cm. Something pops on screen for a fraction of screen and then recovery reboots. It says "no md5 file found". Any chance of zip being corrupt ?
Update 2 -- Now my internal memory has stopped working :/ can't even take a screenshot, nor a photo. says memory full. Doesn't even copy file to memory when connected to pc. Although in recovery mode (twrp) , with usb mounted, it does copy.

nishant_713 said:
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Click to expand...
Click to collapse
weird did u flash normal recovery or gpe recovery ? U have to flash normal recovery and one more thing are u sure that its going into cwm recovery ?
May be the ROM is corrupted buddy download again and flash or try other Roms

Haha. After a hell lot of effort, i did get TWRP installed, and after breaking my head on why cm nightly won't install, i downloaded another one, and it installed fine. Now rocking CM 12.1 (4th device which I'm using on CM, and yet never had so much trouble getting it running..)

Still on 4.4.2 official but rooted. Update???

Hi,
I have a note 3 still on official 4.4.2 but rooted. Since a few days my battery starts draining fast. Maybe it's time to update. Or is it not profitable for such an old device to upgrade to whatever the latest version is?
What is the latest official version for the note 3? And what is the best way to get that? Just unroot and use the update from the system?

You could use a different kernel or try a custom ROM.

Well a few years ago I was change roms constantly on different phones. That was 3 years ago. Now I am not into roms anymore just need a stable phone. Besides I have really no clue how the room installing these days work. Just install from zip in recovery?
Can I do that safe from 4.4.2?

efjbdejong said:
Well a few years ago I was change roms constantly on different phones. That was 3 years ago. Now I am not into roms anymore just need a stable phone. Besides I have really no clue how the room installing these days work. Just install from zip in recovery?
Can I do that safe from 4.4.2?
Click to expand...
Click to collapse
Yes, but you would have to update your bootloader and modem through Odin first for Lollipop and Marshmallow based ROMs to work and boot on your phone.
Running Kitkat bootloader won't make your phone bootup on Lollipop and or Marshmallow based ROMs.
You need a custom recovery of course before flashing a ROM ; TWRP , CWM or PhilZ
(TWRP Method)
Factory Reset your Phone.
Clear Dalvik Cache, System, Cache, Data.
Do not select Internal Storage and Micro SD card, if you do, storage on both internal and external storage would be erased.
I recommend using TWRP 2.8.7.0 as the latest version which is the 3.0.2.0 does not support Aroma Installer.
After you have Factory reset and cleared dalvik cache, system, cache and data.
Now do this
1) Boot into recovery
2) Flash ROM
Done.
With SuperSU ;
1) Boot into recovery
2) Flash ROM
3) Flash SuperSU

LitDesign said:
Yes, but you would have to update your bootloader and modem through Odin first for Lollipop and Marshmallow based ROMs to work and boot on your phone.
Running Kitkat bootloader won't make your phone bootup on Lollipop and or Marshmallow based ROMs.
You need a custom recovery of course before flashing a ROM ; TWRP , CWM or PhilZ
(TWRP Method)
Factory Reset your Phone.
Clear Dalvik Cache, System, Cache, Data.
Do not select Internal Storage and Micro SD card, if you do, storage on both internal and external storage would be erased.
I recommend using TWRP 2.8.7.0 as the latest version which is the 3.0.2.0 does not support Aroma Installer.
After you have Factory reset and cleared dalvik cache, system, cache and data.
Now do this
1) Boot into recovery
2) Flash ROM
Done.
With SuperSU ;
1) Boot into recovery
2) Flash ROM
3) Flash SuperSU
Click to expand...
Click to collapse
OK the so I have to flash 2 times the same rom? Which is the best rom that comes closed to an official untouched one?

I don't understand how to flash the bootloader. Is that installing from recovery? Using install from zip?

For installing bootloader and modem you have to flash with odin.
If you search google then you can find the method how to do it and for bootloader and modem search any latest version of custom rom.you will find the links.
Sent from my SM-G935F using Tapatalk

OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....

Anyone?

efjbdejong said:
Anyone?
Click to expand...
Click to collapse
In my opinion i would say flash lollipop firmware first before you should root it all by odin

efjbdejong said:
OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....
Click to expand...
Click to collapse
Flash bootloader and modem on Odin, it doesn't matter whether you are on Kitkat.
SM-N9005 bootloader and modem :
https://idlekernel.com/flash-tools/firmware/hlte_SM-N9005XX/N9005XXUGPOK2/
Steps before installing a ROM:
1) Download both bootloader and modem from the link given above.
2) Switch off your Phone
3) Boot phone into Download mode by pressing home button and volume down button
4) Connect phone to computer
5) Open up Odin
6) Click on BL and select BL_N9005XXUGPOK2_BOOTLOADER
7) Click on CP and select CP_N9005XXUGPOK2_MODEM
8) Click Start
-----------------------------------------------
Once done, here's how to install a ROM
You have to download a ROM and STORE IT INTO YOUR PHONE before doing this
1) Download TWRP 2.8.7.0
2) Connect phone to computer
3) Open up Odin
4) Click AP, browse to where you have stored the TWRP file/zip and click on it
5) Press Start
6) Switch off Phone and boot into recovery mode by pressing ; Power button, volume up, home button at the same time. Hold it till you feel the phone vibrates twice.
7) Wipe Dalvik Cache, System, Cache, Data and FACTORY RESET.
DO NOT SELECT INTERNAL STORAGE AND MICRO SD CARD.
8) Flash ROM
9) Reboot
-----------------------------------------------
Installing a ROM depends, if it doesnt have GAPPS you have to download it.
If it doesn't comes in with SUPERSU you have to download it. Example ;
Flash ROM
Flash GAPPS
Flash SUPERSU

efjbdejong said:
OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....
Click to expand...
Click to collapse
Don't forget to backup ur whole nandroid before do anything n save it to ur drive computer, trust me
U can use twrp/cwm or flashfire

Stay on 4.4.2, reset to factory, backup first, your battery will be even worst on Lillipop or Marshmellow.
Get a new battery

Just update to 5.0.1, if you still have issues, flash a rom. Also this should've been posted in the Q&A section, or a search would've worked.

Ok I updated now to lollipop thru kies. All went well. Thinking about upgrading to Marshmallow.