Hello,
I wonder if anyone might be able to assist with a problem I am having. I bought a phone sight unseen - I know it's a mistake and I have probably lost money (can't return it) but perhaps it can be recovered/made to work. It says it is a Samsung GT-I5500 under the battery cover.
When I power on the phone, I get the Samsung logo/URL, then the screen says GT-I5500L (not sure why "L" as it is not in the normal model name). Then... basically nothing. Sometimes it works to power off again if I hold in the power button, sometimes not.
I've tried to do a hard reset by holding in vol up, vol down, and power on / hang up at the same time, but it either still goes to the GT-I5500L screen or simply stays at the Samsung screen.
Also tried vol down, middle button, and power on / hang up, with no difference.
I tried installing Kies but I don't think I have the right driver for the phone (Windows 7 can't seem to install a driver). I did install Samsung_USB_Driver_for_Mobile_Phones_v1_3_2200_0.exe but that didn't help in that respect.
I don't really have a preference for whether I'd use a custom/third party ROM vs. stock ROM long term, but I can't seem to get to a point where I would even change the ROM.
Any input is greatly appreciated.
Update...
I just tried again after letting the phone charge a while (looks like the battery was almost empty or all empty when I got it). I tried doing vol down + middle button + power. I got the triangle/Downloading,... screen. I think that's good! Now to research further.
(I loaded up Odin but found it very confusing)
Most recent update...
In the download mode I used Odin. I followed the guide here:
Well, okay, I can't put in the link...
I used the I5500LUYJP2 rar file.
Odin's log said:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> amss download..
<1> 1/5 Finished.
<1> boot.img download..
<1> 2/5 Finished.
<1> recovery.img download..
<1> 3/5 Finished.
<1> system.rfs download..
<1> 4/5 Finished.
<1> csc.rfs download..
<1> 5/5 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
Click to expand...
Click to collapse
However it still won't boot! Just goes back to GT-I5500L.
I tried a hard reset by powering on with vol down + vol up + power but it still went to GT-I5500L.
Another update...
I've been able to use Clockwork Mod via Odin. I can wipe the cache and the davlic cache (I think that's what it's called) though when I try to format /data / do a factory reset it just hangs.
Tried flashing/updating a few ROMs now with nothing that will boot fully yet.
Summary of what works and doesn't work:
Works:
- Going into download mode
- Flashing ROMs via Odin
- Using CWM to apply zip files from SD card
Doesn't work:
- Using CWM to wipe data/factory restore (hangs)
- Any of the ROMs I have tried to use won't fully boot. Includes update-cm-7.1.0-MADTEAM-v1.6-signed, update-cm-7.2.0-RC0-galaxy5-v1.9-MADTEAM-signed, I5500LAROJP2. They get to a point where they either go into a reboot loop or just don't progress to an actual operating system.
Any input is appreciated!
It is clear that there is something wrong in some partition.
If it hangs at data wipe it may be data, cache or sd-ext.
Try removing sdcard.
If it don't help try getting logcat from phone while it is booting maybe we can see which error it is.
Ok the L is for that is a latinoamerican version i think its the same thing that hapened with movil search for the boot rom i haven't the file but i'll search for the file
Enviado desde mi GT-I5500 usando Tapatalk 2
Wiistarman said:
Ok the L is for that is a latinoamerican version i think its the same thing that hapened with movil search for the boot rom i haven't the file but i'll search for the file
Enviado desde mi GT-I5500 usando Tapatalk 2
Click to expand...
Click to collapse
The file is the I5500 XXJF1 that rom flash the startup or i don't know exactly what does but it can help
Enviado desde mi GT-I5500 usando Tapatalk 2
Hey guys..
Help me..
My samsung galaxy5/gt-i5503..
Is hard brick..
I want it back..
Plzzzzzzzzzz help me.....
Sent from my GT-S5360 using xda app-developers app
Boot loop help needed
gargunkle said:
Summary of what works and doesn't work:
Works:
- Going into download mode
- Flashing ROMs via Odin
- Using CWM to apply zip files from SD card
Doesn't work:
- Using CWM to wipe data/factory restore (hangs)
- Any of the ROMs I have tried to use won't fully boot. Includes update-cm-7.1.0-MADTEAM-v1.6-signed, update-cm-7.2.0-RC0-galaxy5-v1.9-MADTEAM-signed, I5500LAROJP2. They get to a point where they either go into a reboot loop or just don't progress to an actual operating system.
Any input is appreciated!
Can you tell me how to fix a boot loop on g5 cause i tried using odin it says amss download all the way and stucked. How to fix using odin ? Help
Click to expand...
Click to collapse
danial93 said:
gargunkle said:
Summary of what works and doesn't work:
Works:
- Going into download mode
- Flashing ROMs via Odin
- Using CWM to apply zip files from SD card
Doesn't work:
- Using CWM to wipe data/factory restore (hangs)
- Any of the ROMs I have tried to use won't fully boot. Includes update-cm-7.1.0-MADTEAM-v1.6-signed, update-cm-7.2.0-RC0-galaxy5-v1.9-MADTEAM-signed, I5500LAROJP2. They get to a point where they either go into a reboot loop or just don't progress to an actual operating system.
Any input is appreciated!
Same ISSUE HERE -- boot loop if flashed with CWM and amss download hang while flashing stock TAR file :crying::crying:
Can you tell me how to fix a boot loop on g5 cause i tried using odin it says amss download all the way and stucked. How to fix using odin ? Help
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Related
I read the previous thread on this, but my situation is a bit different.
I successfully updated to TnT lite using the standard recovery option. I later installed CWM .8 via the Market. I then used CWM's GUI to perform a backup, wipe, and update to VEganLite.
It rebooted me, into CWM recovery screen. but it didn't perform any of the actions. So I manually did a backup, then did a factory data reset, and then choose to install the Vegan Lite.
I ended up with this on reboot:
Code:
Magic Value Mismatch: [ giberish chars ]
[ giberish chars ]
Critical failure: Unable to start kernel.
Unrecoverable bootloader error ( 0x00000002 )
Sometimes it just says "Magic Value Mismatch:", other times I get the more elaborate details above. Seems tied to what type of sleep state it's coming out of.
I can still get into CWM. I've tried to reparition, install vanilla, install tnt, re-install Vegan. All appear to install, and then on reboot I get the Magic Value Mismatch.
So what process should I use next? Low level nvflash? Is there some firmware I can apply via CWM .8?
Seems like I somehow screwed up the non-recovery firmware.
nvflash is a good option. As for root cause, a lot of the mods (and even stock) do not work with newer versions of clockworkmod - you get the mismatch error you are now experiencing. I still use the older .8 bekit version.
Weird, this is CWM 2.5.1.8, I grabbed it through the Market place and it detected me as a G-Tablet.
I'll try doing the bekit version. Can I flash over the current recovery from recovery, or should I go through the NVFlash process?
On my NVFlash files I downloaded, what's the difference between:
nvflash_gtablet_46_2010112600
and
nvflash_gtablet_2010110500
Which should I put on the tablet?
EDIT:
Ok, so I noticed the BEKIT version is:
ClockworkMod 2.5.1.1-bekit-0.8
vs mine 2.5.1.8. Unlucky sub-numbering....
The latest BEKIT appears to be:
2.5.1.3 per: bekit.net
I'm going to try and flash over my current CWM using this.
if it fails, I'll go down the NVFlash path...
Edit 2:
OK, so I tried to apply 2.5.1.3 BEKIT CWM, by copying it onto the internal SD card via USB, and using the CWM 2.5.1.8 to apply it. It applied, rebooted, and now the recovery image gives the bad Magic error.
So it's NVFLASH time....
You should try the older .8 bekit, like roebeet said.
For nvflash, the older one (nvflash_gtablet_2010110500) is generally the better choice, at least from my experience. I tried the newer one once on my newer tablet, and it didn't like it at all - the older one worked flawlessly, on the other hand.
same problem
Hi everybody
I have the same problem. I was running TnT lite and it was working fine. I decided to try the Vegan ROM, so I installed last version of CWM and last version of vegan rom.
I wiped my data, I did a back-up and tried to install the VEGAN ROM. Flashing was successful, but I could not boot. I tried to restore my previous ROM, but it did't work. I was able to boot in recovery mode by pressing Volume+ and ON buttons, but now I'm not able to boot anymore .
I see a black screen with the message: "Magic Value Mismatch:"
I don't know what to do....
OK, so on my G Tab, I had installed the TnT update to the stock rom. It was working great for about 2 weeks or so. One day we went to power up and it just stoped at the first screen with the 3 birds and gives me the Magic Value Mismatch. I tried to reboot holding the power and the vol+ button to get into the system and try to recover from there. No luck. If I let it set for an hour or more and then try to start with the power and vol+ buttons it says it's trying to load a recovery program. It processes for a little bit, takes me to a black screen that says ANDROID on the left mid section of the screen and then goes back to the Magic Value Mismatch error. Occasionally it gives me a couple lines of error info, what appears to be jibberish, but after a few retries it just goes to the Magic Value Mismatch. If I let it set for an hour or more, it's just a repeat. Also on that boot attempt after letting it set, when connected it pops up on my computer for the drive for about 5 seconds and then it goes away. If I try holding the power and the vol- button instead of the vol+ button when connected to my computer it flashes a screen on the tablet and then makes a connection with the computer and stays connected, not showing a drive until I try to restart the tablet. I'm no rocket scientist with this stuff. I'm new to trying to fool around with the roms. Have I bricked this thing or is their a way to make it boot into a recovery mode and reload? I've had the back open, tried the reset button, no luck, tried disconnecting the batteries and letting it sit for an hour and then restart. No luck their either.
AkRyder said:
OK, so on my G Tab, I had installed the TnT update to the stock rom. It was working great for about 2 weeks or so. One day we went to power up and it just stoped at the first screen with the 3 birds and gives me the Magic Value Mismatch. I tried to reboot holding the power and the vol+ button to get into the system and try to recover from there. No luck. If I let it set for an hour or more and then try to start with the power and vol+ buttons it says it's trying to load a recovery program. It processes for a little bit, takes me to a black screen that says ANDROID on the left mid section of the screen and then goes back to the Magic Value Mismatch error. Occasionally it gives me a couple lines of error info, what appears to be jibberish, but after a few retries it just goes to the Magic Value Mismatch. If I let it set for an hour or more, it's just a repeat. Also on that boot attempt after letting it set, when connected it pops up on my computer for the drive for about 5 seconds and then it goes away. If I try holding the power and the vol- button instead of the vol+ button when connected to my computer it flashes a screen on the tablet and then makes a connection with the computer and stays connected, not showing a drive until I try to restart the tablet. I'm no rocket scientist with this stuff. I'm new to trying to fool around with the roms. Have I bricked this thing or is their a way to make it boot into a recovery mode and reload? I've had the back open, tried the reset button, no luck, tried disconnecting the batteries and letting it sit for an hour and then restart. No luck their either.
Click to expand...
Click to collapse
Hi,
It sounds like you're connecting your gtab to a Windows of? If so, you're going to have to install the APX driver from the Nvidia website. I have info in the 1st post here:
http://forum.xda-developers.com/showthread.php?t=914039&highlight=long
You'll then need the files, including nvflash, from bekit's dropbox
http://forum.xda-developers.com/showthread.php?t=861950
Jim
Thanks for getting me started in the right direction. Yes I am using windows. I guess since I'm kind of new to this kind of stuff Im missing something. I'm having and issue on how to launch the NV Flash from the file to get it to push to the Tablet. I click on the NV Flash application and it brings up a small window, and then goes away about as fast as I noticed it. Any suggestions? I had the APX driver driver installed to windows and apparently had the power and vol- button figured out to get the tablet to where it needs to be to be flashed. I've swapped out the bootloader.bin file like you showed to do. Im just not getting the nv flash to launch.
AkRyder said:
Thanks for getting me started in the right direction. Yes I am using windows. I guess since I'm kind of new to this kind of stuff Im missing something. I'm having and issue on how to launch the NV Flash from the file to get it to push to the Tablet. I click on the NV Flash application and it brings up a small window, and then goes away about as fast as I noticed it. Any suggestions? I had the APX driver driver installed to windows and apparently had the power and vol- button figured out to get the tablet to where it needs to be to be flashed. I've swapped out the bootloader.bin file like you showed to do. Im just not getting the nv flash to launch.
Click to expand...
Click to collapse
Nvflash.exe is only a command line apparently, I.e., it doesn't have a GUI. So, you'll need to open a command prompt, cd to the dir, then type the nvflash command line.
I tried running nvflash though the command prompt window and it didn't seem to send anything to the tablet. This is what I got from the command prompt after hitting enter:
C:\Documents and Settings\Norm.AK-F46A8F8F3EDA>c:\nvidia\tegra_froyo_20101105\nv
flash
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config fil
e,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
C:\Documents and Settings\Norm.AK-F46A8F8F3EDA>
It's like it starts the program and then closes. I'm sort of at a loss at this.
Nvfash is the utility that allows you to flash your tablet, you still need to specify what to flash and where to flash it using the command line parameters.
I don't suppose you can dumb that down for a 1 legged frog in a swimming contest? Since I'm not a programmer, it's all greek to me. I think I'm in over my head on this because to type in the command lines, I have no idea what I am to be typing in as a command line. At this point I think I have a brick. Too bad I'm in Alaska and there really isn't anyone local to say here, flash this and make it work.
Deleted bcuz double
AkRyder said:
I don't suppose you can dumb that down for a 1 legged frog in a swimming contest? Since I'm not a programmer, it's all greek to me. I think I'm in over my head on this because to type in the command lines, I have no idea what I am to be typing in as a command line. At this point I think I have a brick. Too bad I'm in Alaska and there really isn't anyone local to say here, flash this and make it work.
Click to expand...
Click to collapse
I'll try...
1) I'm assuming you have the APX driver installed, along w the Windows nvflash.exe, etc. Also you'll need the zip file from bekit's dropbox, the one w 1105 in the filename.
2) unzip that 1105 zip, extracting all the files into the same dir where nvflash.exe is.
3) so now you should have 1 dir w nvflash.exe, the nv*.DLL, etc., along w a bunch of partX.img files, plus others.
4) the same dir should have the right bootloader.bin, gtablet.bct, gtablet.cfg, and nvflash_gtablet.bat
5) start a command prompt and cd to that dir
6) hold vol- on gtab then press power on gtab
7) wait for white screen then black screen
8) on pc, type:
nvflash_gtablet.bat
9) that will do the flash of the entire Gtab
10) probably want to copy/paste the output, in case.
More references, for you:
http://forum.xda-developers.com/showthread.php?t=861950
I have a few Windows-APX-related links in there (I'm an Ubuntu user, so it's all third-party links).
Thanks I'm going to give this a try as soon as I get a chance. I got a hockey game to watch tonight that streams off the computer I'm doing this on and then fix my garage door that blew a spring (when it rains it pours). I'll let you know how I did. Thanks so much!!!
I had a moment to try this before the hockey game. When I ran nvflash., the black screen on the tablet flashes the following:
Entering nvflash recovery mode / nv3P Server
Then it disconnects it’s connection from the computer and the CMD window shows the following:
C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105>"nvflash.exe" --bct fla
sh.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3C000011
--create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x1700618341c08597
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x3c000011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MSC
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: USP
creating partition: UDA
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MSC please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 USP please wait.. done!
Formatting partition 11 UDA please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed
Press enter to continue:
Now when I press the power and Vol- button no white screen comes on. However I can hear the chime on the computer telling me it is connecting and disconnecting and can run the nvflash over and over with the same results.
Hmmmmmmmm……. It looks like it is trying to work but something is not working as it should…. Possibly a corrupted file in the downloaded files? I'm going to try to download and set up again a bit later. The adventure continues...
I uninstalled what I had installed from the computer, deleted the downloaded files, redownloaded the files, extracted and traded out / added in the files as you guys showed, plugged in the tablet, and watched it work and flash back the stock rom and complete all tasks. Then success, Viewsonic and G Tablet screens and back to original. It updated to the latest rom which won't work with the TnT enhancement rom I had used. But at least it's working again. I'll have to do some reading on the other roms available. Even with the latest update from Vewsonic in the past week it's laggy compared to what it was with the TnT enhancement. Also no app market without the software :-( This has been a learning experience for sure and I'm still not a Jedi yet on this stuff! I just wanted to say thanks for the help and thanks for posting to help a cross eyed, dyslexic rookie in trying to rescue our G Tablet!
AkRyder said:
I uninstalled what I had installed from the computer, deleted the downloaded files, redownloaded the files, extracted and traded out / added in the files as you guys showed, plugged in the tablet, and watched it work and flash back the stock rom and complete all tasks. Then success, Viewsonic and G Tablet screens and back to original. It updated to the latest rom which won't work with the TnT enhancement rom I had used. But at least it's working again. I'll have to do some reading on the other roms available. Even with the latest update from Vewsonic in the past week it's laggy compared to what it was with the TnT enhancement. Also no app market without the software :-( This has been a learning experience for sure and I'm still not a Jedi yet on this stuff! I just wanted to say thanks for the help and thanks for posting to help a cross eyed, dyslexic rookie in trying to rescue our G Tablet!
Click to expand...
Click to collapse
Glad you got it working! So do you think the earlier nvflash problem was bcuz of a bad download? And re-downloading and nvflashing worked?
Jim
Hi - trying to update my Galaxy Pro on Three to Gingerbread. Using Odin and its stuck on
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
I can't reboot my phone - just get a picture of phone and PC connection. HELP !!!
Using
B7510XXKPB_B7510XXKP3_B7510XXOXAKP4_HOME.tar.md5 with Odin 4.38
I can't get into recovery mode, only into Download Mode.
Urgent Help please!
On this root tutorial http://www.broodplank.net/rootsamsungi9001.php you can download a ABD file. That file should contain a "RebootRecovery.bat" file. When your phone is connected to your pc it should help you get into recovery mode.
Did you wait long enough while flashing? Odin says "closing com port" (or something like that) when it's done.
flashkash said:
Hi - trying to update my Galaxy Pro on Three to Gingerbread. Using Odin and its stuck on
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
I can't reboot my phone - just get a picture of phone and PC connection. HELP !!!
Using
B7510XXKPB_B7510XXKP3_B7510XXOXAKP4_HOME.tar.md5 with Odin 4.38
I can't get into recovery mode, only into Download Mode.
Urgent Help please!
Click to expand...
Click to collapse
enter download mode again.
Just download any other odin downloader for your mobile , this should pretty much end the problem
if not use different usb port, your problem will be solved.
Sent from my GT-B7510 using xda premium
Hi bro... I m using gt-b 7510 and I want to upgrade this phone.....it is possible if yes than how to do this and it is sucessfully installed..?
HI
Hi My Samsung GT B7510 doesnot boot, doensot even show the charging light when connect via the USB cable, no reaction, please help
Naseer
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks
Preparing for a clean (with loss of data) installation LineageOS 14.1 + TWRP-3.1.0-0
Attention! The warranty is now invalid.
It's to delete all your data (programs, contacts, SMS ...)
Make a backup to external media or PC first.
Preparation:
- First you need to install the drivers. The phone must be determined by the computer.
- Kies must be stopped (if it is installed on the computer).
- It is desirable to disable antiviruses, firewalls and similar software.
- Use only USB rear ports (for a laptop it does not matter).
- It is desirable to use the original cable (why - I do not know, but many so advise).
- It is desirable to charge the battery by at least 50%, full charging is welcomed.
Instruction:
1. Install Samsung_USB_Drivers_for_Mobile_Phones
2. Unzip the folder Odin3_v3.09 and transfer it to the root directory C:
Run Odin3 v3.09.exe as administrator and select all as the screenshot :
- In the PIT field, insert the file - I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit.zip
- In the PDA field, insert the file - lp-kernel-14-03-CWM-for + ODIN.tar
Turn off the phone. Enter the device into the boot mode by pressing simultaneously the Volume Down, OK, Power ON / OFF buttons, confirming with the Volume Up key the desire to flash.
Then, we connect the phone to the computer, the ID field: COM should light up in blue, then press the START button.
A successful solution, you will see the word "Pass"
3. Disconnect the phone from the PC, transfer it to the CWM recovery mode.
That there were no problems with the internal memory (SDcard0), we format it:
- mounts and storage -> format / storage / sdcard0 -> default
Do a full system cleaning:
- wipe data / factory reset
- mounts and storage -> format / system
4. In the recovery process, install the files:
- TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip
+
- kernel-Lanchon-20160406-i9100.zip
5. Reboot and log in to TWRP.
6. Do not forget:
ROM - https://download.lineageos.org/i9100
+
OpenGApps - http://opengapps.org/
The following files were used in this manual:
- @arnab
- @the.gangster
- @Lanchon
THANKS!
Teams of : TWRP, Lineage OS.
Do all the credits to them.
I just wrote the instructions.
Good luck.
hello .. i followed your tutorial and i am on lineageOS now
however is there any method to cancel the sdcard0 entirely ?
i added a 64 GB SDcard and used the adoptable memory to increase my internal storage .. however whataspp still uses sdcard0 to store its folder !
any clues ??
how to root ????
hadid90 said:
how to root ????
Click to expand...
Click to collapse
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
toy_story said:
Look here - https://forum.xda-developers.com/showpost.php?p=71684593&postcount=21
Set in TWRP: addonsu-14.1-arm-signed.zip
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
Click to expand...
Click to collapse
i didnt know i had to go to develoeper options and enable it thank you
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
hadid90 said:
about the sdcard0 .. i found my answer here
https://forum.xda-developers.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651
Click to expand...
Click to collapse
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
toy_story said:
I'm glad that you are doing well.
Be careful with "[MOD] Switch from non-emulated to emulated internal SD card", first read the entire stream.
I used it before, but because of certain problems, I stopped using it, and did not advise it on your question asked above.
Click to expand...
Click to collapse
It's working very well here.. but you need to be careful on how to install the ROM .. i also used my external sd card to put the zip of lineage and gapps on.. it's the only way. I also used 50% of my sd card as an internal storage .. it s working pretty well
I followed the descriptions but my S2 won't get over the startingscreen of Lineage OS. There is always just this circle going from right to left on this arc. How long should I wait?
Thanks guy, very useful for someone who wants to install LOS on his S2 in 2017
Hi,
I tried to copy the files (TWRP-3.1.0-0-recovery-the.gangster-IsoRec-i9100.zip, kernel-Lanchon-20160406-i9100.zip, ROM lineageos.org/i9100 & OpenGApps) to the SD using my computer but my SD card adapter had a problem. I now have a new adaptor that works but am now stuck with all the files on the SD card ready to go but I can not boot into recovery to install the file. When I boot the phone I just get the startup screen with the Samsung logo and a yellow triangle. If I do the key presses to get to recovery with the phone connected to the computer and running odin then I can connect and reflash CWM but after that I cant boot into recovery to do step 5.
Any help appreciated,
Thanks,
Mark
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ? i flashed the stock rom using odin but the S2 boots and stays on samsung logo animation for hours haha .. should i use the stock pit file and use the repartition option ? i heard that may brick the device .. any guides ? i ve searched but all threads are very old with dead links etc
hadid90 said:
ok i have done playing with my moms old S2 .. i need to return it back to its orginial latest stock rom .. any guides on how to do that ?
Click to expand...
Click to collapse
Look here:
- https://forum.xda-developers.com/showpost.php?p=71481676&postcount=587
- https://forum.xda-developers.com/showpost.php?p=73126683&postcount=48
Phone bricked! Help!
Bricked my phone for the first time while following the steps here!
Need help!
This was an old phone. I had Sentinel ROM installed. I had smashed the display years ago and just got it fixed a month ago. Since it was old so I did a factory reset from the Android settings. After that I got stuck in bootloop.
Didn't get much time to tinker with it for some time, till few days ago.
I had CWM installed. So at first I tried installing LineageOS by using option "installing from sdcard" from CWM recovery(This was before coming across this tutorial). It failed that time (I had tried a few times). I tried doing factory reset, wipe dalvik, format /system etc etc couple of times.
I think it always used to come out with some error:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Then after that I tried flashing TWRP ([RECOVERY] [ISOREC] [TWRP 3.0.2-1] [OFFICIAL] [26/04/2016]) following the 2nd installation instructions (Flash via HeimdallSuite (Windows only)) from this thread: https://forum.xda-developers.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457
This also failed with this error:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Then I came across this present tutorial. I had a lot of trouble trying to get ODIN to detect the phone plugged in via USB in download mode (i.e. to get ID field: COM in blue)
Somehow after a lot of tries with different USB cables, and reinstalling drivers and restarting Windows, finally it got detected. So I carried out the instructions ditto as in guide but I faced another error:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I unplugged the phone, closed ODIN and tried to retrace the same steps (I'm not sure if I restarted the phone during this time).
Now again it wasn't getting detected in the download mode.
So finally I switched off the phone and tried to get into Download mode. I couldn't do it. Then I realized that nothing was working. It wasn't even starting normally to the "Sentinel ROM" logo. Tried charging the phone and realized that even the charging battery icon doesn't show/indicate it is being charged.
That's when I realized that it was hard bricked (totally dead). If I plug it in charger, it gets heated up.
Can somebody please help unbrick my phone?
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
bersem said:
That was a misstake !
<ID:0/014> Re-Partition operation failed.
This Tutorial @toy_story is great, so you cannot do wrong.
You have to come in download mode. Do not give up. Try it several times. If you can not make it, get a USB-JIG and try it out. You can buy it on the internet, but you can also do it yourself. For that you need quiet hands and a soldering iron.
Click to expand...
Click to collapse
Yea I know the re-partition was the part where things broke.
Can't enter download mode anymore.
I guess will have to try getting a USB Jig. The only hope left I think, unless somebody has some other suggestions..
Endless boot
EDIT: Never mind -- I fixed it by restoring to the stock ROM and PIT file then trying again. All works perfectly now!
-----------------------------------------------------------
I followed the instructions here, and everything seemed to work fine with no errors. But when I finally boot the phone into Lineage OS for the first time, the animated loading image appears but the phone never boots.
I waited over 2hrs yesterday. Today I restored the original PIT, wiped the phone and tried again. The phone has been "trying" to boot for an hour now, but the boot animation just keeps on going.
:crying:
FWIW, the phone already had Lineage OS on it, but I wanted to use this installation method as it seems to increase the partition used for installed apps.
I'm not sure what to try next or how to figure out what went wrong. Can anyone help?
Notifications LED
Hello,
After performing this install, the LED that lights up when charging and whent there's notifications does not work.
Instead, the touch buttons light up. I haven't seen any options in settings to change this.
Is there any app that where I can tweak these settings? Or is it something with the recovery/kernel?
Apart from that, it works good so far!
Thanks
EDIT:
Just realized galaxy s2 has no notification led, I was thinking of my other phone
--edited--
Sry, nvm..
@toy_story At point 5, or better at the beginning (what is needed for this procedure) you should add that you need a micro SD card on hand. Wasn't obvious for me, and I didn't have one....
Other thing, my GT-I9100 just hangs at the splash screen with the yellow exclamation sign now I must admit that I was a bit tired yesterday while I wanted to follow the instructions (connecting it to Odin and putting all files in the designated slots worked the first time, and it also booted into the CWM recovery, I did all wipes also)... After trying to figure out how to follow step 5 I stumbled through the CWM menue and activated some option by accident (kinda annoying way to navigate it I must admit), causing the phone to reboot. And now, I'm stuck with the above mentioned scheme. At least it turns off when I hold the power button longer, turning it back on will again produce the same scheme.
I connected it again to Odin and started over from point 1 but the problem retains. What can I do?
scragnothh said:
@toy_story What can I do?
Click to expand...
Click to collapse
Look here -
https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?