Related
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
devsk said:
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
Click to expand...
Click to collapse
ignore sig. reflashed 1.3.1. when i cp /sbin/gzip /sdcard/gzip i get cannont stat /sbin/gzip no such file or directory
edit: i found gzip in /system/bin. just take off .txt extension.
Thanks for you efforts. But the problem is I need the static binary that was present in the 1.3.1. The one in /system/bin is a dynamic one and won't run (tried it already) in 1.4 recovery.
I need to figure out where did that static binary in 1.3.1 come from. That binary is 3 times faster in compressing than the one in busybox.
sorry i couldn't find it. did you try asking cyanogen?
david1171 said:
sorry i couldn't find it. did you try asking cyanogen?
Click to expand...
Click to collapse
He is on vacay until the weekend is over.
erissiva said:
He is on vacay until the weekend is over.
Click to expand...
Click to collapse
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
B-man007 said:
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
Click to expand...
Click to collapse
Thanks guys, you are awesome!
Hmm... [No Luck]
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
rikupw said:
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
Click to expand...
Click to collapse
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
devsk said:
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
Click to expand...
Click to collapse
yes, it is safe, the ONLY issue i've had is I cannot seem to be able to successfully edit a recovery.img and reflash it, it works, the only issue is I don' thave command I get the "A N D R O I D" when i try to use terminal at the recovery menu, (although everything works via adb)
I am on 1.4, I just downloaded ALL the Cyanogen.zips (I hope I don't overuse his bandwidth, I would feel so bad...) but I found no recovery images within his .zips,
try flashing a 1.3.1, (I'm not able to use my android phone, as I left it at work haha)
and trying which. just m ake sure you do a nandroid backup before you flash back to 1.3.1 (though I doubt it should make a difference)
Code:
IDEA!
try to mount all your partitions within the recovery command (from the phone, not adb).
type
# mount -a
(it'll error, don't worry its normal )
# exit
press enter, and then type "which gzip"
I think that its actually loading the /system/bin/gzip... which would make sense... but idk, can you give it a try?
*EDIT AGAIN*
ok, the reason for what I told you, is that I noticed that if you reset the terminal (exit, enter) its like re-adding the PATH to the shell, i guess? I'm still a wee bit new to linux, but I know how to search (or rather... scower)
How can I get my infuse back to stock using a mac? I have tried heimdall front end and the Heimdall One-Click with no success. If there are step by step instructions on how to do this it would be greatly appreciated. I have searched and can't find much info for doing it on a mac. I have the infuse4g-backtostock-one-click.jar but when I click to open it just closes. I have restarted pc, reset permissions, updated java, put phone in download mode. Am I doing something wrong?
Open it in commands line. Open a terminal window and CD intro the directory. Type Java -jar backtostock.jar or whatever thename of that file happens to be. Clearly you didn't read the thread good enough, but at leeway you found the thread.
You may also need to set up codeless kext or something but I don't have a Mac so I don't know how to do that.
What happens when you try to run heimdall frontend?? And you can run heimdall in command line as well. Linux bozo went over that in the kj2 thread. The only difference is you won't need boot.bin or sbl.bin but may have to add param.ifs too the list. If test it to give explicit instructions but my power is out. I'm posting form my phone.
The java I get unable to access and when i put phone in download mode and open the oneclick stock boot infuse.jar file it just flashes on dock then quits. Heimdall front end gives tar header contained invalid file size. I am wondering if I can use the stock rom for i900 with heimdall such as XWJSD 2.2.1 with heimdall seeing I cannot find one specific to infuse?
thorn292 said:
The java I get unable to access and when i put phone in download mode and open the oneclick stock boot infuse.jar file it just flashes on dock then quits. Heimdall front end gives tar header contained invalid file size. I am wondering if I can use the stock rom for i900 with heimdall such as XWJSD 2.2.1 with heimdall seeing I cannot find one specific to infuse?
Click to expand...
Click to collapse
Obviously you are using heimdall wrong. Did you try laughing one click from command line? That's how you nerd to open it, its covered in the thread.
Heimdall needs heimdall specific packages if you use a .tar. Don't do that plus i9000 roms don't work. Get the Odin package gtg made and extract the.tar I would make a heimdall package if I though anyone was gonna use it, but people don't like change even for the better, it drives me nuts.
heimdall 1.3 has 3 tabs, one is labeled "flash" open that tab. Get infuse.pit this is the only pit file that works. Then there is an add button, it will give you a selection of partitions to add. when you add a partition you need to add a file to that partition, the files vs partitions are as follows
zimage-kernel
factoryfs.rfs-factoryfs
Param.ifs-param
dbdata.rfs-database
Csc.rfs-cache
Modem.bin-modem
I'm going off memory and there may be a couple mistakes, but once you see how it works its not hard to see where stuff goes.
If you don't feel comfortable with that then get heimdall 1.1. Just extract the Odin .tar file and add files in the GUI., it really explains itself. I dislike the new GUI, the old one was easy. The command line us easy too but i'm not sure I remember the commands exactly right.
Do I need the odin exe to do this or can I just use the file? I cannot run exe files.
thorn292 said:
Do I need the odin exe to do this or can I just use the file? I cannot run exe files.
Click to expand...
Click to collapse
No just the .tar. Extract it and flash the files inside using heimdall.
If you can't figure it out you can get boot camp and run window.
I'm obviously not doing something right every time I extract the file in Heimdall 1.1 I get errors. Would AT&T put the stock rom back on if I took it in to them?
Update: I borrowed a windows pc and got it up in running back to original in about 30 minutes. Thanks for ll your help.
thorn292 said:
I'm obviously not doing something right every time I extract the file in Heimdall 1.1 I get errors. Would AT&T put the stock rom back on if I took it in to them?
Click to expand...
Click to collapse
glad you got it but no att wouldn't do that. ROM flashing voids any type of warranty or insurance, sometime people get away with sending phones to Samsung if they get bricked, if you do that sort of thing make sure the phone doesn't even turn on or boot past the Samsung screen. The repair people probably don't have much time for diagnosis and would simply flash to stock and send it out the door.
Can someone who has webtop tar up thier osh and post a place I can grab it.
I have been working to get a full version of ubuntu going in webtop, and I was working on reverse engineering the way they did it with the bionic and that did not work well
I will buy a beer or coffee for anyone who can do this for me.
Thanks,
Jim
just got home. give me a few minutes
what file format you want?
You rock, does not matter much, a tar or zip or 7zip or bz2... whatever you put it in I can take it and put it back in place from there.
Thanks,
Jim
lol. while it was pulling, i was messing around with my phone and crashed it..
re-pulling
OSH.IMG.TGZ
dd if=/dev/block/webtop of=/mnt/sdcard/osh.img
did you get it?
Yes, I did. I also gave a donation to you.
THANK YOU!
Jim
I was able to get my webtop working again, by whacking tomoyo, that is the Linux FACL that they are using for webtop.
Thanks again for your help.
Jim
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
matthewsteross said:
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
Click to expand...
Click to collapse
it think it's a dd image, so just do the reverse;
dd if=osh.img of=/dev/block/webtop
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
matthewsteross said:
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
Click to expand...
Click to collapse
This thread was from before we had the FXZ files to flash from fastboot.
I believe the proper way to restore webtop would be to grab the 55.11.16 release FXZ. Extract it and extract moto-fastboot to the same directory. Run a cmd and cd to the directory.
Put your phone into fastboot mode by holding volume down while you power it on, hook it up via usb, and
(or you can use the two button salute and choose it from the boot menu)
Code:
moto-fastboot.exe flash webtop grfs.img
You can then use motorola's faux-55.13.26 update to reapply the patches to update the webtop partition to the 55.13.25 version.
This tar.gz file would still work, you'd need to decompress it, adb shell into the phone, run su (to get root) and then run the commands from the directory where the img is stored. I don't think you need busybox to run dd... could be wrong
Flashing with fastboot is the more elegant solution.
(note it's probably not a good idea to write the img files from the fxz directly with dd.)DON'T CROSS THE STREAMS!
I got it to work by flashing in fastboot, thanks for all your help! All is well again and I even have Linux unlocked and running the XFCE-4 desktop environment. Thanks for all your help!
I ran 'unlock.su' and an unlock code came up about a page wide.
Is this correct? Seems a bit long to me.
How and when is the unlock code entered?
dlw
Read this post.
http://forum.xda-developers.com/showthread.php?p=15810793
Sent from my SGH-I997 using xda premium
Thank you for replying.
I do not have Windows. I have Ubuntu 12.10.
That's a problem I'm having. Everything seems to be for Windows.
I do have a hex editor. Will see what I can find out with it.
The problem now is adb can't find device.
Turn phone off then back on.
Debugging mode is on.
Enter 'adb devices',
List of devices attached
0123456789ABCDEF device
Enter './unlock.sh',
Raging Against The Cage...
error: device not found
Been searching for hours.
dlw
dlw1146 said:
Thank you for replying.
I do not have Windows. I have Ubuntu 12.10.
That's a problem I'm having. Everything seems to be for Windows.
I do have a hex editor. Will see what I can find out with it.
The problem now is adb can't find device.
Turn phone off then back on.
Debugging mode is on.
Enter 'adb devices',
List of devices attached
0123456789ABCDEF device
Enter './unlock.sh',
Raging Against The Cage...
error: device not found
Been searching for hours.
dlw
Click to expand...
Click to collapse
make sure you're rooted.
follow the link psal gave you. follow the op direction
google for hex 10 editor
once you have the bml3 on your sdcard, upload to cloud, email yourself a copy etc..just get a copy to your pc...adb is not needed.
follow the rest of op direction to get ur code
I do not have Windows. I have Ubuntu 12.10.
Did not find a '010 hex editor' for Linux.
I have 'ghex' which is a Linux hex editor.
I do not have a /dev/block/bml3, there is a /dev/block/bml12.
Opened bml12 in ghex editor.
searched for 'FFFFFFFFFF0100000000'.
It is not there.
Posted the above at the unlock site at 9:00 am, no word back yet.
I've been at this for hours.
My apologies if the post is wrong in any way.
dlw
dlw1146 said:
I do not have Windows. I have Ubuntu 12.10.
Did not find a '010 hex editor' for Linux.
I have 'ghex' which is a Linux hex editor.
I do not have a /dev/block/bml3, there is a /dev/block/bml12.
Opened bml12 in ghex editor.
searched for 'FFFFFFFFFF0100000000'.
It is not there.
Posted the above at the unlock site at 9:00 am, no word back yet.
I've been at this for hours.
My apologies if the post is wrong in any way.
dlw
Click to expand...
Click to collapse
the code is in /dev/block/bml3
I must be dumb as a box of rocks.
There is not a /dev/block/bml3
There is /dev/block/platform, /dev/block/vold.
A lot of *loop*,*mmcblk*,*ram* files and one bml12 file.
I am looking at the /dev/block/ directory now in 'rootbrowser'.
What am I doing wrong?
dlw1146 said:
I must be dumb as a box of rocks.
There is not a /dev/block/bml3
There is /dev/block/platform, /dev/block/vold.
A lot of *loop*,*mmcblk*,*ram* files and one bml12 file.
I am looking at the /dev/block/ directory now in 'rootbrowser'.
What am I doing wrong?
Click to expand...
Click to collapse
can't see like that.
download terminal emulator (TE)
run TE
type "su"
type" dd if=/dev/block/bml3 of=/sdcard/bml3.bak
look for it on the sdcard
Entered this 3 times:
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Get this error:
/dev/block/bml3: cannot open for read: No such file or directory.
dlw1146 said:
Entered this 3 times:
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Get this error:
/dev/block/bml3: cannot open for read: No such file or directory.
Click to expand...
Click to collapse
i just did it and got the bml3.bak file
make sure you are rooted..and on froyo, gb or ics stock samsung partitions..not jb
My rom is JB -Slim3.0.0
No idea about partitions.
dlw1146 said:
My rom is JB -Slim3.0.0
No idea about partitions.
Click to expand...
Click to collapse
if you really need the code, you will need to go back to 2.2.1 or 2.3.6 with root and try again.
you can also try to find the infuse jb's bml3 partition location.
i don't run jb so i can't help u there.
gl
Yes, I need the code. AT&T's reception is not good here. A new tower just went up last week close by but its Verizon.
Thank you so much for your efforts. You have helped me learn a lot.
Thanks again,
dlw
try this...
i had trouble using the unlock post also. try using this post ---> http://forum.xda-developers.com/showpost.php?p=14887023&postcount=166
It was WAYYYYY easier for me and the code was in plain sight.
With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14