Hello all and a good day.
Device: Samsung Galaxy Note 8.0 GT-N5100 (3G) - XME (Malaysia)
What I did: Nothing unusual! Device mainly used for text reading and some writing. After updated to Android 4.2.2 (PDA: N5100XXCMI1, CSC: N5100OLBCMH2, MODEM: N5100XXCMI1) via ODIN, the symptom # 1 appeared. The firmware for Malaysia was downloaded from the sammobile.com.
Same time I came to know the importance of /efs backup, so rooted (1st time) the device, backed-up /efs via EFS Pro, used Triangle Away, unroot, and flashed the stock. Since the symptom # 1 continued, I did a factory reset, and then all other symptoms appeared.
Symptoms:
1) Tablet doesn’t vibrate.
2) Kies is unable to detect the tablet.
3) SIM Cards are not detected. A prohibition sign is shown at the cell signal (left to the battery indicator) (see image 1).
4) In “Settings > About device”, and in “Settings > About device > Status”, many fields are stated as “Unknown”, e.g.:
Baseband and IMEI (see image 1 and image 2). Incorrect Serial number (/efs has the correct one as in the back cover).
5) Camera view is upside down.
6) Proximity sensor doesn’t work. In the *#0*# Test mode, Proximity value is 1.0. If exit and check again value becomes 0.0.
7) Regardless of Flight mode or not Cell standby drains the battery a lot. Once activated, Flight mode turns grey (see image 3).
8) [SOLVED, see 5th post] Several times (not always), a white screen appeared at the boot screen (model name), and also when plugged to power source while the tablet switched off. I guess something to do with param partition.
9) [SOLVED, see 5th post] "No command" error message in the stock recovery (3e).
9) “Modem boot timeout” and “Couldn't find 'rild' socket” errors in logcat -b radio.
10) When tried to use the tablet as a modem from Windows 7, it gives an Error 692, and the diagnostics states, “Timed out waiting for response from modem”.
Solutions tried (no success): As many, I too tried various /efs based solutions mentioned in XDA, and flashed all the five firmwares available for the device, but the problem stays same. I tried to solve this without troubling others much, but now I am lost.
Help needed: Is this problem can be fixed by me with some guidance, which would be great since to claim warranty the tablet need to be send to another country. Or is it a hardware problem, therefore I should send it straight to Samsung service without wasting more time?
Attached files, if they help:
1) Outputs of the following commands
logcat -b radio
logcat *:E
dmesg
ls -la /efs
ls -la
mount
cbd -t xmm626x -o t
2)
- recovery log from - CivZ_rev1.1-PhilZ 5.1.1 (touch)
- build.prop file
Thank you for reading. Greatly appreciate any help and guidance. Sorry, if I violate any XDA rules in this post. Kind regards!
New Problem: "There is no PIT partition."
Last night managed to fix a part of the problem (customer.xml error in logcat) in the above post thanks to the guidance from civato. In an attempt to fix other problems, last night I had mistakenly executed the following cmd in ADB while in recovery.
Code:
dd if=/data/media/0/efs.img of=/dev/block/[B]mmcblk0[/B]
The correct one should have used is mmcblk0p3 (/efs partition in Note 8.0). At least I managed to do some damage, otherwise all the credit goes to Samsung.
Now I can go to download mode only. A white screen flashes if try recovery mode or normal boot or even connect to a power source to recharge. Since charging or not also unsure (before this happened battery was 100%), I have a limited time to use the device to get it to work properly. Other problem is, if fail, can’t claim warranty as there’s no way to use the Triangle Away in this situation.
Now when try to flash via ODIN:
1) normal way - it failed stating, "There is no PIT partition." (see image 1).
2) with kona3g.pit I have - it failed stating, "Re-partition operation failed." (see image 2).
Even when the device was working properly, 2nd option never worked for me.
My kona3g.pit read well by PIT Magic 1.3.10.
Can anyone provide me a working .pit for Note 8 GT-N5100. Thinking of trying Heimdall Suite 1.4.0 tonight, but need some reading as I never used it and limited battery time for flashing.
Any advice to recover my device is highly welcome.
King regards.
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Working kona3g.pit for GT-N5100
civato said:
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Click to expand...
Click to collapse
Brilliant and thank you! The Odin3_v3.07.exe you provided missing an Odin3.ini (see image). I used an Odin3.ini (see attached files) that I have (for the same version) together with your Odin3_v3.07.exe and kona3g.pit, and the flashing went perfectly without any errors. So your kona3g.pit is a genuine working one. Thank you
I’ll continue further tonight and post here. My friend share his laptop with me, therefore I have limited time.
EDIT: When looked from the PIT Magic 1.3.10, the GT-N5110.pit is same as the GT-N5100 one (kona3g.pit). But when looked from the HxD - Hexeditor 1.7.7.0, the signatures at the end of the files are different, so it might not work on the sister device. Also, your GT-N5110.pit has trailing zeros after the signature, somewhere I read that these zeros must be deleted from a hexeditor for it to work.
Kind regards!
Image:
Solutions for symptoms 8 & 9
Solution for symptom 8:
Googled for a param.bin for Note 8.0, but only found one for Galaxy S3. Anyway, being fed up with the white screen, I copied S3 param.bin to the mmcblk0p4 partition of Note 8.0, surprise it worked. But the boot screen became S3 . Later among my backups, I found a param backup of mmcblk0p4 that I took via EFS Pro. Unfortunately couldn't restore it via EFS Pro as I had renamed the tar.gz to keep things tidy. So I extracted it to get a file called param. Since this param didn't work after copying, I compared it in the hex editor with the working S3 param, and noticed EFS Pro add some data to the beginning of the file. I removed this begining data and also the trailing zeros, and renamed it to param.bin (to go along with the name in kona3g.pit, perhaps not necessary). Finally, copied it by "dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4" command, after couple of reboots white screen disappeared.
Solution for symptom 9:
Difficult to say this is a solution but it disappeared after this. In order to send for warranty claim, I restored the device to clean stock. First used Triangle Away to reset the counter. Booted and fully unroot via SuperSU. Then flashed the stock rom with the pit file, and without restart option. Shut down the device and boot into the recovery to do a full wipe, and the "No command" error wasn't there.
I must say, since my modem not working, capslock66's Android Reverse Tethering 3.15 saved my day to download the required Triangle Away add-on via laptop's broadband connection.
Since all other symptoms couldn't be solved my me after much effort, I sent the tablet for Samsung service.
Related
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."
cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.
Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet
rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?
VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.
I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route
perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job
oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)
This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App
thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T
Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.
ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!
TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.
hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks
sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?
KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?
samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?
VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.
(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado
Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado
Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!
steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425
I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)
Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?
steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..
waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.
I just picked this up and it's build number P5220XXUAMI2 out of the box.
I'm a little confused regarding firmware versions and I've found a few threads for the P5200 and P5210 builds, but nothing for the P5220. Is it possible to root and flash a custom recovery on the model/build I have?
Sorry of this is a super n00b question. Tablets are not my strong point.
EDIT:
I was able to root using the method here
http://forum.xda-developers.com/showthread.php?t=2432467
I wasn't sure it would work as the files are for the P5210 but it was fine.
thank you!
@ebue
I am trying to help ebue to find out exactly what this OLDDDD tread is about:
What is the safe way to root a GT-P5220 Tab3 10 4G .
I decided to move here to stop hijacking ( not really) or taking to much attention for P5220 on the original question of ebue at => http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157
So in this tread we have the ONLY testimony in this forum, where our friend parker_dhd claims he got it
parker_dhd;48219938...[COLOR="Red" said:
I was able to root using the method[/COLOR] here
http://forum.xda-developers.com/showthread.php?t=2432467
....
Click to expand...
Click to collapse
Now it is true that http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157 is an old and abandon thread. But we can guess that in fact as expected P5220 share same partition arrangement for recovery.img with P5210/P5200. Be careful with what I said. I am talking only about recovery.img. There are in fact some other partition that are specifically different like for example the modem one.
Still many had ask the same. In particular I saw moonbutt74 in another thread asking the same compatibility question I have:
moonbutt74 said:
S,
could you tell me jf the following is correct on the 5220 ?
/system = /dev/block/mmcblk0p8
/data = /dev/block/mmcblk0p9
/boot = /dev/block/mmcblk0p10
/recovery = /dev/block/mmcblk0p11
thanks, m
Click to expand...
Click to collapse
The answer is easy to find if we get a Champion owner to help us. I am hoping @ebue can help us help him.
Well at the moment I do not have a good internet connection I am really limited in bandwith.
So we need a champion that can download a Stock Samsung 4.2.2 Firmaware. In particular I need the recovery.img.
So @ebue
1)You should had downloaded a Stock Rom yourself just in case you need to go Back to Stock.? Don't you?
2)Clearly in your case your Stock Official Samsung Rom will not start with
5210xxxxxxx_P5210Xxxxxxx_xxx.zip instead will be with "5220" or something 5220xxxxxxx_P5220Xxxxxxx_xxx.zip
Listen still the name may be in another format. That is the usual name for sammobile files.
3)In my case I downloaded: 5210UEUAMH1_P5210XARAMH1_XAR.zip long time ago.
4)In my case if I can unzip this file I will see inside 2 files:
P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5
SS_DL.dll
Ignore "SS_DL.dll"
5) Now extract "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5"
6) Now Rename the extracted "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5" to "P5210UEUAMH1_P5210XARAMH1_HOME.tar". Yes no ".md5"
7) Now open "P5210UEUAMH1_P5210XARAMH1_HOME.tar" with winzip or any other zip app. You will see it contains
"boot.img, cache.img, hidden.img, recovery.img and system.img". ".
8) Now Extract just/only "recovery.img. And using winzip/winrar Zip ONLY "recovery.img" to "recovery.zip".
We zip it back because this forum will not allow to upload files that are not in zip form.
It should be a file of less than 20Megs. Usually around 10megs. Uploads files are done tru "Manage Attachments" link at the bottom on the advance Replay window.
Listen If you have trouble uploading it to this forum you can try to upload in
Code:
http://d-h.st/
9) Post that file in here, so that i can look at it.
Please see that you may have to use Code to not show your Hot Link like this
Code:
http://d-h.st/
Ok,
I spent my time overnight to download a P5220 Stock rom. I did
P5220XXUAMJ8_P5220VFGAMK1_VOD.zip
I think is a Vodaphone from Germany. But as I said the Recovery Info that we need should be the same in all roms.
1) Warning
Now before I say anything more, I want to make clear that there are many people with Tab3 7", 8" and even 10" that claims that had no trouble installing recovery and rooting. But when they decided to go back to Samsung Stock they lost Wifi or Cell capabilities. I know sound serious, and I have no Idea why so many claims. Lets say more, Most of those claims you can find them here in QA and are 7" and 8" that has nothing to do with the TWRP used in 10". I just have to say this because I seen it and have no understanding on the facts.
I will strongly suggest to backup modems and efs partitions as soon as you install a recovery. This can be done using dd command under Recovery. We could even make a update.zip to do that if any is interested.
You need to be sure that you have downloaded your exact Stock Rom. Even more If I was in your case with a Tab3 with cellphone capabilities I will take my Stock Rom and eliminate the modem.img from the package. There is no reason as to have that in the Stock Rom, unless you have in fact a bad modem. This is only my personal opinion. This is personal suggestion from some one that have no Idea of what he is saying. It is opt to you to research in the area.
Click to expand...
Click to collapse
I have compare "fstab.recovery" from both P5210 and P5220 and show exact information.
/recovery emmc /dev/block/mmcblk0p11
I guess we can conclude that all P5200, P5210 and P5220 have "recovery.img" in "/dev/block/mmcblk0p11"
Code:
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p2
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
[COLOR="Red"]/recovery emmc /dev/block/mmcblk0p11[/COLOR]
/modem emmc /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
2) So the first question: Can I install and used a TWRP Recovery made for P5200 or P5210 in P5220? Its seems yes, you can install and used it.
3) BUTTTTT
There is no TWRP or any other Recovery that had been made specifically for P5220. So once install your Recovery will think it is a P5200 or P5210 depending in the file you use.!!! This may result in that some "update.zip" type of installation will fail due to mismatch of Model. This should not be a big problem. You can always install back your Stock Recovery. And we can ask moonbutt74 to build a TWRP recovery using the P5220 particular files in ramdisk of recovery.img.
4) If you want to root I sugest you fallow the only sucefull claim in this forrum, see first post of this thread. I will the install Recovery from
http://forum.xda-developers.com/showpost.php?p=45552913&postcount=1
Then I suggest you backup your sensitive partitions using dd if TWRP do not have that capability.
and I guess you can then root using
http://forum.xda-developers.com/showthread.php?t=2642796
Please stick around, I am very interested in getting a copy of you pit file. I had made a WIN7 batch file that will copy that file from your tablet. A soon as you are rooted notify us and I will post the batch file.
I am attaching the recovery.img of P5220 in Odin tar.md5 in the hope that @moonbutt74 can help us, As soon as moonbutt74 has a P5220 you could upgrade as a TESTER! and report your findings.
This is great news because I was having problems trying to copy the requested files from my phone. So I can just go ahead and install the 'Odin_SGT3_recovery' from the thread you linked. Then use Rest3ssroot.zip to root, right? Or should I just wait until moonbutt74 looks at the file?
Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
moonbutt74
There a bunch of good I mean good developers here that I bet you are double as smart as moonbutt74. jijiji I am kidding I do not know.
But what I know is that moonbutt74 will take a problem by himself and spent hours, days,weeks.. until hi find the solution. I admire him.
I do not know why any of the developers had comment yet, I can assume that the lack of FEEDBACK from P5220 owners reporting the result make us be in safe mode. But believe they are out there watching us. jijiji
You know moonbutt74 had read this, look at the thanks. He has been around. But please understand that he has not commit to create for you a new recovery!! I have faith that he will help P5220 in the near future. But when I do not know. So if you what to wait, that is smart. I just do not know when it will happen.
Listen this is what I am going to do. I am going to test the P5220 4G Stock Recovery I downloaded in my P5210 wifi. I see how it behaves. This is not a fill probe that it can work, but at least we can see if the TAB bootloop failing!
As for procedures.
Remember I am no expert!!! If you want to follow me is at you own risk.
Please understand the difference in installing a Custom recovery.img (TWRP) vs root process.
*Just installing Custom recovery.img (TWRP).
First booting in recovery do not affect normal boot process(Android). Is like a X-ray, you can inspect and take x-rays ( backups) without injury Android OS. You cam always replace the original recovery.img and no harm done.
** rooting - Is like an organ replacement operation at the table, you are installing new software that Android could reject and bootloop!!
A) So first step:
Download and have ready all tools and files. No harm done to the TAB3.
B)Watch this video: it is for TAB3 7" but give you an Idea of the procedure you need to follow:
Code:
http://youtu.be/BDShwBHRjUE
C)installing
[RECOVERY][TWRP_2.7] SGT3 Recovery[FINAL]=>http://forum.xda-developers.com/showthread.php?t=2442915
1) Once you download file you received:
Code:
recovery.tar.zip
2) Unzip you will see:
Code:
recovery.tar.md5.tar
this is the file will be using with Odin.
If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.
Odin
1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown in Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acknowledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "recovery.tar.md5.tar"
9) "Message" window . Odin tell you the status in this window. you should see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.
11) Now after you see Successful Odin is ready. If you do not see there is something wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automatically since we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS.
16) navigate if you like to see your new recovery
Now do not install root yet. Just use TWRP to backup to External SDCARD. yes external so that if something fails you still have recovery files in your External SDCARD.
So once you have done this report to us.
Good luck.
ebue
Keep an eye on moonbutt74. He have not make any comment but, he just edited his thread today around 03:52 PM around 4 hours ago.
And I see a link that reads
Code:
dev-host link - http://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN -extract then flash.
Usually I do not post other user work "Breaking News", but if I am you I will wait to see if he in fact is helping you!.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
I feel like I am talking by myself.
But I have to say that I did test the STOCK P5220 Recovery and it seems to work nicely. Clearly I have a "Custom" Rom and Recovery shows the Triangle over Android!! Tha we know it happens.
I did also test new h__p://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN in my P5210 for test purposed and Philz seems to work correctly too.
I did extracted "recovery.img" from "TO RECOVERIES - GT-P5220 ODIN" and seems to shows correct data for P5220 device.code="santos10lte".
At this point I still like TWRP because moonbutt74 TWRP has the ability to accept adb shell commands on the PC! A nice addition while testing.
r2d23cpo said:
Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
Click to expand...
Click to collapse
Although I have been a registrant since the said date, I am still a novice. I have no technical ability what so ever. I am kinda busy with my family and work constantly. My kids do not give me a lot of time to do trails and errors and I do not have so much time on my hands. That is why I thought a root would have been available for download so I can just root and get on with my life. I do not have time to experiment lie you guys do. All I want to do is root to remove apps that I do not use or want. That's all. I used to try out different different ROMs a long time ago. But that is when I had time. I do not want to be bother with trying out different ROMS if I am not forced to. That is why I leave these things up to people who have the time and resources and who are dedicated to these things. So, if I have to wait to get a proper root so I do not have to risk anything, than I will. So, I can give you the little info that I have for my pad. Here they are:
1. I have downloaded Odin already and in the process of downloading my Stock Firmware.
2. I do not have an external car yet for my pad. Only for my Note 3, which I am using. I will buy one soon.
2. My Android -Version is 4.2.2 ; Basbandversion is P5220XXUANE1 ; Kompileringsnr is JDQ39.P5220XXUANB4
Anything else you request?
I understand you, not enoght free time. Do not feel presure from me. Wait for others to report a valid solution is no bad, in many cases is the smart thing todo.
As I said moonbutt74 build Philz Advance CWM for P5220. But some one with a P5220 need to test it and report. I see in his last page some interested, but if no one reports we will never know. Reporting Feeback is the most value tool after a developer has done his work.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I just tried Moonbutt's Philz and TWRP recoveries. I was trying to flash the stock roms for p5220)LTE as posted by Restl3ss. In both cases I got errors and am now waiting for a TWRP version that works on the p5220.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
---------- Post added at 04:32 PM ---------- Previous post was at 04:04 PM ----------
quijote1 said:
OK, I installed PhilZ and it seems to work fine. First I tried to flash your deodexed rom. Part way through the flash I got the message:
set_metadata_recursive: some changes failed
E;Error in /sdcard/download/P5200-4.4-stock-deodexed-rooted.zip
(Status 7)
E: Installation aborted
So now I'm going to try the totally stock one.....
Same error again. Bummer because I forgot to make a PhilZ backup of my 4.2.2. I have a TWRP backup, but that's all.
Click to expand...
Click to collapse
The above is a message that I sent to Restl3ss, but repeat it here since it shows the error messages that I got with Philz by Moonbutt.
Just to provide feedback, the version of Philz recovery worked very well for the most part. I like it better than TWRP. If I could get it to install roms, I would stick with it.
Off topic, I am in Spain and Orange is my carrier but my tablet is not linked to Orange. There is a stock rom on Sammobile that is for Orange in Spain. Would that work on a tablet that is unlocked?
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
To add more detail, it turns out that Restl3ss left out a few lines of code for the p5220. Since he didn't have one he never noticed. Now he has added that code and now his rom loads with TWRP.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
My tail of woe. From what I have read there is nothing that can be done but I thought I would ask anyhow.
I was overseas with an SGH-T999L, and took it to a man in a market to be unlocked. 2 hours later it was useless. The man said it would be OK once it was back in the US, but it wasn't. Obviously he didn't keep backups.
Dialing *#06# gives me "null/null".
I cannot turn on wifi (I slie the switch and it slides right back) but can turn on bluetooth, gps and nfc.
Baseband version is "Unknown"
Build number is JSS15J.T999LUVUBNC1
It appears that he used vRoot to get root.
According to the "odin screen"
CUSTOM BINARY DOWNLOAD: No
CURENT BINARY: Samsung Official
SYSTEM: STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
I used this article from techglobal101.wordpress.com 2013/05/02/how-to-solve-no-service-on-samsung-galaxy-s3/ following the imei already corrupt steps to generate
the text file with the imei in it. However the NV Reader/writer has problems. Firstly *#7284# only gives me a choice of "Modem" or "PDA". However *#0808# does give me more options including "RMNET + DM + MODEM". The bigger problem is that the SPC code of 000000 is not accepted, so NV reader/writer can not access anything.
Looking in the /efs filesystem (using "adb shell" and "su" and "busybox find /efs -size +1000k" ) does not find any files larger than 1MB (I believe the nv_data.bin should be at least 2MB) so no original ".nv_data" file, no "nv_data.bin" nor "nv_data.bak". There are smaller files, for example there is a file /efs/imei/mps_code.dat, 3 bytes long containing TMB. The /efs partition is 13716 blocks in size and is only 33% full (4556 blocks in use).
I can use adb to install and uninstall packages, and copy files.
Things which look interesting to me in the output of "getprop" are (with a valid sim card installed)
[DEVICE_PROVISIONED]: [1]
[gsm.operator.alpha]: []
[gsm.sim,state]: [NOT_READY]
[gsm.sim.unknownready]: [1]
So far I have not done anything else. In particular I have not tried using ODIN to download a stock image, nor have I tried removing the files which are in /efs.
I also have not tried creating a 2MB file of NUL characters called /efs/nv_data.bin in the hope that that would at least advance the solution.
I would be pleased to get any good advice on what to do next. Please assume I know my way around a unix command prompt, but this is my first venture into the world of Android.
First thing, don't mess with the efs. It's not relevant to the issue at hand and sounds to be just fine. Most of the NV Data is stored on different partitions. Don't assume its the same as on other devices like many others seem to advise.
Second, download your stock firmware (NC1)(root66 firmware is ok), flash via Odin on your computer, and factory reset (will wipe internal sd). This often fixes these problems without having to touch the NV data.
Something tells me that whoever you took it to may have tried to flash the 4.1.1 modem to use our free unlock method. If so, that will cause the exact same thing you are experiencing now.
If after that it is still not fixed, PM me and I will try to help get your imei restored. We are not allowed to post information, tools, links or further discuss that here, so if it comes to that, I can only help you via PM.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
Click to expand...
Click to collapse
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
IMEI
jooo91 said:
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
Click to expand...
Click to collapse
My baseband is ok but my IMEI is "unknown " does this mean there is hope
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
bonebeatz1234 said:
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
Click to expand...
Click to collapse
is it the modem.bin which is extracted from the ROM (tar.md5 file which we put on odin's AP) ?
i've tried it, but no luck :crying: