[HACK] Root for I9000XXJPC inside - Galaxy S I9000 Android Development

This was getting buried in the original I9000XXJPC thread, so for those that missed it - here is the root I9000XXJPC
Thanks to johoe for advice on the tar
http://www.multiupload.com/GJEZ1OT9NN
Extract and copy update.zip to /sd of phone
Run Odin with Auto Reboot UN-checked, loading the i9000_Kernel.tar as PDA
Put the phone into download mode and flash the i9000 Kernel.
Pull the battery. reboot into recovery mode and flash the update.zip you put in the root folder of your sdcard.
Pull the battery again, reboot into download mode again.
Run Odin with Auto Reboot checked, loading the I9000XXJPC_KERNEL.tar as PDA
reboot.

Confirmed functional
Thanks

<3 for this one. Had jpc flashed pretty fast while hoping for a fast root method.
it became true

Hi!
I have the following problem with Odin:
First it hanged for a while in SetupConnection and then Failed.
Dug around old threads and did what someone else had done, compatibility mode XP SP3 and running as admin. Though I wouldn't do that if you're having the same problem:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it won't boot normally, nor in Recovery. Download mode works though, so I do have a chance of not having a brick for a phone, do I?
Is it a problem with drivers or what? I noticed it's using COM8 instead of COM11 as I recall it using previously.
Request for immediate help. Thank you.

I'm new to Odin, never had to use such apps with my htc desire...
Anyhow, when trying to flash the pda, getting this:
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Any ideas?

Pesticle said:
Hi!
I have the following problem with Odin:
First it hanged for a while in SetupConnection and then Failed.
Dug around old threads and did what someone else had done, compatibility mode XP SP3 and running as admin. Though I wouldn't do that if you're having the same problem:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it won't boot normally, nor in Recovery. Download mode works though, so I do have a chance of not having a brick for a phone, do I?
Is it a problem with drivers or what? I noticed it's using COM8 instead of COM11 as I recall it using previously.
Request for immediate help. Thank you.
Click to expand...
Click to collapse
Really not sure what went wrong, it worked fine for me and many others. you will have to flash back to an older firmware or wait for the odin version of JPC to be released

Newbie mistake! All should go well from here on.
I HAD KIES ON!! Which was taking up the COM port ofc. So close your Kies like someone who's done some flashing before :l

jaketurbo said:
I'm new to Odin, never had to use such apps with my htc desire...
Anyhow, when trying to flash the pda, getting this:
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Any ideas?
Click to expand...
Click to collapse
Is your phone in download mode? hold power + volume down + home until your phone loads up the yellow download screen

It works! Thanks buddy.

I also had Kies on...
duh

i did everything but and the update.zip seems to install correctly but i can`t see the apk and i receive FC when using app that require root...

did you remember to flash the I9000XXJPC_KERNEL.tar after the update.zip?

In the readme file, it says to pull out the battery, but you can simply just hold the Power button for 10 seconds. Saves removing the case and battery

yes i did put the I9000XXJPC_KERNEL....
superuser is somehow working, lets say i can make a screenshot with shootme but after saving i receive FC from superuser..
i read that if i cant install the market version i need to remount the partition and delete the superuser.apk but "adb remount" is not working

Sucess! Weeeii!

I have big problem...
i have update.zip on the sd
i open odin set pin and keave blanck auto reboot but tap on re-partition.
launch i9000 on pda
flash is ok
leave the battery and lanunch in recovery mode
try to alaunch update.zip and give to me an error
unable to mount \dev
and reboot on recovy...
i have try more times also try to wipe all data but do not work....
what is the problem ????

flashing the new froyo
I followed the direction as they are and everything ran fine with no errors however after i do everything and im rebooting for thet last time, the phone stays on the galaxy S screen and it keeps vibrating but it wont go any futher. any help you guys

Very nice, thanks a TON for the effort.

Code:
E/AndroidRuntime( 9651): FATAL EXCEPTION: main
E/AndroidRuntime( 9651): java.lang.RuntimeException: Unable to start activity Co
mponentInfo{com.noshufou.android.su/com.noshufou.android.su.SuRequest}: android.
database.sqlite.SQLiteException: no such table: permissions: , while compiling:
SELECT _id, allow FROM permissions WHERE from_uid=? AND exec_uid=? AND exec_comm
and=?
E/AndroidRuntime( 9651): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2663)
E/AndroidRuntime( 9651): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2679)
E/AndroidRuntime( 9651): at android.app.ActivityThread.access$2300(Activi
tyThread.java:125)
E/AndroidRuntime( 9651): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:2033)
E/AndroidRuntime( 9651): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 9651): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 9651): at android.app.ActivityThread.main(ActivityThrea
d.java:4627)
E/AndroidRuntime( 9651): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 9651): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 9651): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:871)
E/AndroidRuntime( 9651): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:629)
E/AndroidRuntime( 9651): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9651): Caused by: android.database.sqlite.SQLiteException: no
such table: permissions: , while compiling: SELECT _id, allow FROM permissions W
HERE from_uid=? AND exec_uid=? AND exec_command=?
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteCompiledSql.nat
ive_compile(Native Method)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteCompiledSql.com
pile(SQLiteCompiledSql.java:91)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteCompiledSql.<in
it>(SQLiteCompiledSql.java:64)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteProgram.<init>(
SQLiteProgram.java:80)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteQuery.<init>(SQ
LiteQuery.java:46)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteDirectCursorDri
ver.query(SQLiteDirectCursorDriver.java:42)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteDatabase.rawQue
ryWithFactory(SQLiteDatabase.java:1454)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteDatabase.queryW
ithFactory(SQLiteDatabase.java:1338)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteDatabase.query(
SQLiteDatabase.java:1293)
E/AndroidRuntime( 9651): at android.database.sqlite.SQLiteDatabase.query(
SQLiteDatabase.java:1373)
E/AndroidRuntime( 9651): at com.noshufou.android.su.DBHelper.checkApp(DBH
elper.java:33)
E/AndroidRuntime( 9651): at com.noshufou.android.su.SuRequest.onCreate(Su
Request.java:56)
E/AndroidRuntime( 9651): at android.app.Instrumentation.callActivityOnCre
ate(Instrumentation.java:1047)
E/AndroidRuntime( 9651): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2627)
E/AndroidRuntime( 9651): ... 11 more
it seems like its database error.. any suggestions ?

I get the app installed but when i run it it gives me a black screen. Plus the phone seems alot slower after installing it.

Related

[RECOVERY][CWM] Completely stock ClockworkMod 5.5.0.4 (7/6/12)

This is a clockworkmod recovery built completely from source. It has the latest cwm updates and the latest ics kernel (eMMC erase bug fixed). This should also have the hanging backup bug fixed. I havent had time to make a billion backups to test this but the few i did without the .hidenandroidprogress file worked like a charm If you do get a hanging backup that is all koush's fault as i just used his latest sync to cwm.
To get adb working on this:
add these lines to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
-add them in the section that says [Google.NTx86] and the section that says [Google.NTamd64]. just make it look like the ones that are already there but with this code:
Code:
;
; Samsung Hercules
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0231&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
- then right click "my computer" and go to device manager
- you will see a driver with a yellow exclamation point...right click it and click "update driver software"
- click "browse my computer"....then click "let me pick from a list of device drivers on my computer"
- then click all devices
- click "have disk..."
- go to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
- click to allow installation of driver
- presto
DOWNLOADS:
recovery.img / recovery.tar.md5​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CHANGES:
Changes here.​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
so no one tried this?
Excellent.. Thank you... Now if somebody could just put the ADB together with the CWM that would be proper... thanks Man.
Can you *please* elaborate on the instructions for ADB. Just put some WinDex on it... I want my ADB back..
Sent from my SGH-T989 using xda premium
Is this your own version of the CWM included in ROM Manager? Can you make sure it's updated in ROM Manager? It sounds like this one is much better, I hope it becomes default
updated to latest commits by koush
sk8erwitskil said:
updated to latest commits by koush
Click to expand...
Click to collapse
Thank you very much! Your work is much appreciated!
You first lolz
Recoveries made from ics kernels scare me still
Sent from my SGH-T989 using Tapatalk 2
Flashed via Odin w/o a problem here
Code:
<OSM> Enter CS for MD5..
<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..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
Adb works just fine as well
Code:
C:\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
43492893 recovery
C:\android-sdk\platform-tools>adb shell
~ # ls
ls
boot init sbin
cache init.qcom.lpm_boot.sh sd-ext
charger init.qcom.sh sdcard
data init.qcom.usb.sh sys
datadata init.rc system
default.prop lpm.rc tmp
dev proc ueventd.goldfish.rc
emmc res ueventd.rc
etc root
~ #
Made a backup and then restored from backup; all good

N7105 - Only get into Dowload-mode after Update

Dear Community,
I stucked with my Samsung N7105 since 2 days , so im requesting for your power & knowledge
After Updating the phone i dont get any response, i only have access to the download-mode, which output is:
Code:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I installed the samsung usb-driver 1.5.43 and tried Odin 3.07 / 3.09 to get CWM (CF-Autoroot) on it. Device was detected, but odin is requesting for a PIT-file, so i gave him this one
http://forum.xda-developers.com/showthread.php?t=2137008
also tried the one from Dr. Ketan (which seems to be the same)
http://d-h.st/hwQ
output from odin (tried different versions & usb-ports):
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So i tried Heimdall, from the official source http://glassechidna.com.au/heimdall/, because of the better debug-output in command-line.
First step was, getting/printing the PIT...failed - It seems Heimdall also getting no response (connection-problem?). Im abit unsure with the usb-drivers. As described I replaced the samsung driver with zadig.
But in Zadig i have two options , which seems to be related to the samsung-drivers. "CDC Abstract Control Model" & "Gadget Serial" --> I replaced the 1st one with the libusb-win32(v1.2.6.0) Drivers.
There are also libusbk(v3.0.5.16) & WinUSB(v6.1.7600.16385) for choice, but as i understand Heimdall is using the libusb-win32-Libary(?)
Trying to get/print the PIT with Heimdall I get the following:
G:\samsung\heimdall-suite-1.4.0-win32>heimdall print-pit --no-reboot --usb-log-level warning
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
libusbx: warning [winusbx_claim_interface] auto-claimed interface 0 (required to claim 1 with WinUSB)
Setting up interface...
Initialising protocol...
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
libusbx: warning [libusb_exit] some libusb_devices were leaked
Click to expand...
Click to collapse
Is he claiming the wrong Interface? Steady I get a little frustrated, have someone any idea or are there other methods to get informations from the phone...flashing a a new recovery on it?
U need to install rescue firmware 4.1 which was uploaded by steff in dn3 latest post
I created the thread on how to recover bricked note 2
You can read in first or second page
I am travelling so at the moment I can't upload the recscu firmware but u can request steff195 to upload this here
It has full rom image plus pit file u can fix your phone via 3.07 odin
Then u can flash any stock 4.4.2 to bring it back to bug free life
And then rooting and etc
Sent from my GT-N7100 using XDA Premium 4 mobile app

Someone please help with rom flash issues

ok so far i unlocked bootloader so im a dev N910z
i flashed custom kernel: N910F-Stock_Kernel_XXU1COJ3_Root_Permissive_NTFS_PhilZ_v2.0
and i flashed TWRP: twrp-3.0.2-0-trltevzw.tar
after stock rom flash attempt via odin i get:
on odin:
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on phone:
sw rev check fail: [aboot] fused 2 > binary 1
[1] emmc write fail: ABOOT
on adp side load:
cannot read file
I cant get the phone to flash any roms Via: twrp, download mode or odin....
please someone tell me what im doing wrong... i just want a debloated stock rom/or at least a stock rom (i used a debloater app and i guess i deleted something that prevents games from loading) i would like to via text if that is ok with whomever is willing to help... im matt my cell is 843 9901111 PLEASE HELP im a newb haha
Double check and make sure the bootloader is unlocked.
Sent from my SM-N910V using Tapatalk

Soft brick - cannot flash via recovery or Odin

Basically woke up with my phone as a brick... phone crashed when my alarm was supposed to go off (luckily I was already awake) and now hangs on the boot splash screen.
Device is an i747m, previously running S3Rx 3.0 (Android 4.3) with MK5 bootloader and modem. CWM 6.0.4.7 installed.
I am able to boot into both recovery and download mode.
However, in recovery mode, I get the errors:
Code:
E: Can't mount /cache/recovery/command
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Furthermore, if I try to factory reset, I get the error:
Code:
Formatting /data...
Error mounting /data!
While in recovery, I am not able to flash a new recovery or ROM. There are no errors when flashing, however, after rebooting nothing has changed. I'm assuming that's because the system cannot access the storage.
Through Odin, I can flash TWRP with no errors. However, once I try to boot into recovery, I am still on CWM 6.0.4.7.
Through Odin, I am unable to flash ROMs (trying to flash 4.3 MK5 stock rom). I am using Odin 3.07 on a W7 x64 computer with Samsung drivers installed and an official Samsung USB cable.
I receive the error:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
It appears that there is a problem with the internal memory since I can't read/write, but I am unsure if it is fixable.
I have come across this thread, but I am skeptical if it will work since it is for the Verizon S3.
I also came across this thread in my research, but I can't get cygwin to download >.> It seems promising, but I am unable to try it at the moment.
Any help or suggestions would be greatly appreciated. Please let me know if any additional information is required.
Have you tried flashing a 4.4.2 ROM?
audit13 said:
Have you tried flashing a 4.4.2 ROM?
Click to expand...
Click to collapse
Yes, I have tried flashing the 4.4.2 NE6 ROM using Odin with the same result (NAND write fails).
I have also tried flashing via Heimdall. No success there either. Heimdall is able to upload the file to my device (according to the progress bar), but then terminates with, ERROR: Failed to confirm end of file transfer sequence!
Also, the PIT file I extracted from my device via Heimdall does not match a "normal" i747m 16gb PIT found on the internet... I also cannot flash the 'normal' PIT onto my device (same error as above).
It's possible the internal memory chip is damaged which is not easy to repair. Simplest fix may be to buy a used s3 with a smashed screen and do a motherboard swap.
Yeah, that's what I'm thinking too at this point since I can't get anything to write onto the memory. I just loaded up Aroma File Manager through recovery and it looks like most of the files on my internal memory are gone, even though I have not been able to successfully factory reset through recovery. At least I have TiBkps of everything.
Do you think I could franken-phone using an i9100 (international model S3)?
Boot into download to find out.

[Q]N7100 - internal storage is listed as 0MB, Odin Complete(Write) operation failed

First, sorry for my bad Eng
I flashed my phone with some rom cook for N7100 and It running smoothies, but this morning, my phone auto restart and stuck at logo screen. I get into TWRP and find there is no OS and no internal memory, after try everything(I known), last chance I used Format Data, but It still not working. Tried to flash other Rom, even stockrom by Odin, but it gets:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I recorded the video too but I dont have enough post to post link, so sorry:
/watch?v=U8V_3aRfucw (youtube)
Updated video:
https://youtu.be/U8V_3aRfucw
Logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Internal Storage 0MB:
Wipe failed:
Data Format failed:
SD Card folder empty:
I really need help to solve this problem. Please help me.
Thanks.
manhtidus said:
First, sorry for my bad Eng
I flashed my phone with some rom cook for N7100 and It running smoothies, but this morning, my phone auto restart and stuck at logo screen. I get into TWRP and find there is no OS and no internal memory, after try everything(I known), last chance I used Format Data, but It still not working. Tried to flash other Rom, even stockrom by Odin, but it gets:
I recorded the video too but I dont have enough post to post link, so sorry:
/watch?v=U8V_3aRfucw (youtube)
Logo screen:
Internal Storage 0MB:
Wipe failed:
Data Format failed:
SD Card folder empty:
I really need help to solve this problem. Please help me.
Thanks.
Click to expand...
Click to collapse
Go to wipe click data click advance click change file system to fat32 and go to wipe again click advance click file system and click ext4 done
Or
Try Odin best guide
xress7 said:
Go to wipe click data click advance click change file system to fat32 and go to wipe again click advance click file system and click ext4 done
Or
Try Odin best guide
Click to expand...
Click to collapse
Thanks for reply, I tried that too but always notice:
Code:
Updating partition details...
"Failed to mount '/efs' (Invalid argument)
"Failed to mount '/cache' (Invalid argument)
"Failed to mount '/system' (Invalid argument)
"Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
And Odin failed too.
Someone please help....
Sorry for spam but help me please, I don't know find where to help
Odin fails when trying to install sboot.bin for one or all of these reasons:
the ROM is not made for the phone;
need to use the original Samsung USB cable;
need to use a different USB 2.0 port;
the ROM's bootloader is older than the bootloader in the phone; and/or
the phone's memory chip has failed and you need to replace the motherboard.
Did the ROM come from sammobile.com?
audit13 said:
Odin fails when trying to install sboot.bin for one or all of these reasons:
the ROM is not made for the phone;
need to use the original Samsung USB cable;
need to use a different USB 2.0 port;
the ROM's bootloader is older than the bootloader in the phone; and/or
the phone's memory chip has failed and you need to replace the motherboard.
Did the ROM come from sammobile.com?
Click to expand...
Click to collapse
The "phone's memory chip" part is the scariest part and I hope its not
I used "RESURRECTION REMIX [5.8.0]" Rom, and I tried flash Stock Rom N7100XXUFNI4_N7100OLBFNI1_XXV but it failed.
And I don't understand part "the ROM's bootloader is older than the bootloader in the phone". Where can I check it?
You confirmed that the phone model # is gt-n7100 in download mode? Did you get the stock firmware for the n7100 from here: https://www.sammobile.com/firmwares/database/GT-N7100/ ?
audit13 said:
You confirmed that the phone model # is gt-n7100 in download mode? Did you get the stock firmware for the n7100 from here: https://www.sammobile.com/firmwares/database/GT-N7100/ ?
Click to expand...
Click to collapse
Yes, I downloaded the stock firmwave form Sammobile,
Download mode screen showed:
Code:
ODIN MODE
PRODUCT NAME: GT-7100
CURRENT BINARY: Custom
SYSTEM STATUS: Offical
KNOW WARRANTY VOID: 1
RP SWREV: A2
Sounds like the memory chip could be defective.
Try flashing twrp 2.87 and see if that works. If it doesn't work, you can try a cell repair shop to see if they can force flash it.
audit13 said:
Sounds like the memory chip could be defective.
Try flashing twrp 2.87 and see if that works. If it doesn't work, you can try a cell repair shop to see if they can force flash it.
Click to expand...
Click to collapse
Still cant flash it:
Code:
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just like the phone refuse to change anything in it :crying:
If cant find any solution, so last chance is bring it to store and pray
I admit it doesn't look good.
A cheaper solution may be to buy a used phone with a smashed screen and working motherboard.
Thanks for your helping.
I'll look for some chance from terminal or adb sideload, bad thing is last night it still working perfectly. so sad
manhtidus said:
Thanks for reply, I tried that too but always notice:
Code:
Updating partition details...
"Failed to mount '/efs' (Invalid argument)
"Failed to mount '/cache' (Invalid argument)
"Failed to mount '/system' (Invalid argument)
"Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
And Odin failed too.
Click to expand...
Click to collapse
Try pit for odin
xress7 said:
Try pit for odin
Click to expand...
Click to collapse
I'm finding PIT file for flash, but still get this:
Code:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe not right PIT file, I flashed 2 file "PIT_N7100_16GB_20121102.pit", "t03g_0907.pit" found on internet, but not working
Looks like you'll have to either take it to a cell shop or replace the motherboard.
Tried to use adb sideload to install other recovery, install perfect but after restart seem nothing change.
Tried change timezone on TWRP, but after restart, it did not save changes.
Same happened with my note 2 tried every thing but Nand is corrupted .there are only 50% chance .
Wow, I guest I'm the first one get this error:
After find out can push file to mobile by adb push XXX, I tried reinstall rom, and alot of stuffs to test, now I get this error when use "Data Format" on TWRP: "Unable to get block size for wipping crypto footer." and still
"Unable to wipe data
Unable to format to remove encryption --> I guess I need to do something in here
Failed to mount /efs, /cache /system /data
Unable to mount storage
Hope someone will help my resolve this
Update:
Sadly, After reboot phone, everything gone, nothing saved.
In my /dev/block/ there is no file mmcblk0p0 - 16 , just have loop0-7, ram0-15

Categories

Resources