Hello everyone
i was trying to deodex the stock rom 4.4.2 italy (T211)
after flashing the deodex zip i created
the tab went in to recovery boot loop
this happened with me when i flashed a mod for t211 which worked totally fine on 4.1.2
what is wrong?
is it because of the zip file or the kitkat stock rom..?
Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app
loopiness for everybody ....yay
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param
andynroid said:
Sammy has left a signature in our Tab....now we can no longer root and mod even though you come back to JB
Sent from my SM-T211 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow, thats weird
but i think that devs here would surely come up with something
moonbutt74 said:
e.r.,
please describe your process from flashing to recovery loop as clearly and descriptively as possible.
one thought is some sort of mutual check going on between boot and recovery
another is tampering with fusedlocation.apk is a guaranteed loop.
i dl'd the boot.img and will let you know if i find anything.
sorry to impose further but i might need recovery.img as well.
m
Click to expand...
Click to collapse
sure
i flashed the stock kitkat
then booted (welcome screen and stuff)
booted to download mode and flashed a custom recovery (philz cwm)
download that root zip (chainfire 1.94 update) and flashed it
while leaving the recovery, it asked for
prevent system from erasing root something
i choose
fix root
then it booted
downloaded supersu and blah
then was deodexing the rom
got the kitkat deodexer
created a zip file
then went to recovery and flashed it
then reboot to system
again the same fix root issue
selected fix and recovery boot loop
no worries bro
here you go
love to help
https://drive.google.com/file/d/0B21rpre8LhJ6c0RGYmhqbjVWZEE/edit?usp=sharing
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param
moonbutt74 said:
i also need your block layout with labels, remember i don't have this device.
i want to know what this is; symlink /dev/block/mmcblk0p7 /dev/block/param
Click to expand...
Click to collapse
You mean the content in the folder ?
EDIT:
you want me to upload those files ?
ah
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m
moonbutt74 said:
e.r.,
run cat /proc/partitions > /sdcard/cat-part.txt
or similar to get list of your devices mmcblk's by name
or if you have parted on your device run
parted /dev/block/mmcblk0
then wait for
(parted)
and type print all
copy and paste into text and post.
m
Click to expand...
Click to collapse
run where?
terminal emulator..?
ethical ricado said:
run where?
terminal emulator..?
Click to expand...
Click to collapse
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m
moonbutt74 said:
yes, if you can without root.
so just to clarify, you booting into recovery repeatedly OR when you boot to recovery you tab hangs?
if i understand it correctly the failure of a critical process/service will trigger panic/reboot
m
Click to expand...
Click to collapse
give me a min
everything works smooth
nothing hangs
EDIT:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 12288 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1472512 mmcblk0p14
179 15 204800 mmcblk0p15
179 16 204800 mmcblk0p16
179 17 5640192 mmcblk0p17
253 0 358400 zram0
179 48 4096 mmcblk0boot1
179 24 4096 mmcblk0boot0
179 72 7761920 mmcblk1
179 73 7760896 mmcblk1p1
?
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img
moonbutt74 said:
e.r.,
i don't understand, your response did not answer my question.
are you saying that you do not have an issue?
m
on a side note; i didn't find anything jn boot.img even suggesting a script/execution of a script.
it's my hope that you have retained the firware in question because i would like you
to crack it open and see if there is a new BOOTLOADER img included, not boot.img/kernel.img
Click to expand...
Click to collapse
yeah, no issues
this are the contents
https://drive.google.com/file/d/0B21rpre8LhJ6VzU1T2RZOUo4Q0E/edit?usp=sharing
??
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it
moonbutt74 said:
e.r.,
umm so if there is no issue then there is nothing that needs to be done.
as for the image showing the list if you reflash you ORIGINAL stock firware and then pickout the boot,system,images and flash them alone you might break the root-break samsung tried to pull, BUT if there is no issue then there is nothing to do.
based on your responses do you see where i'm confused?
m
on a side note here is a modified boot.img, ro.secure=0 adb.secure=0 and system should be mounted system rw [maybe]
http://d-h.st/search?search_by=1&search_for=t211-modboot
not recovery flashable, you need to dd write it
Click to expand...
Click to collapse
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens
Noooooooooo
ethical ricado said:
The only issue i faced so far was the recpvery boot loop
And i guess that might be because of the wrong zip file
But will try your method tomorrow and see what happens
Click to expand...
Click to collapse
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m
moonbutt74 said:
e.r.,
okay DON'T do that skyelm just told me there's a lot more in this firmware than the original stock, meaning your bootloader
is already overwritten and original stock will not correct that. we need someone still running original firware to
pull/dump their first and secondstage bootloaders if i'm starting to understand the actual ****edupedness of this mess.
what would be good is to shoot me another pic of what's in the original firmware.
m
Click to expand...
Click to collapse
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2
okay
ethical ricado said:
Gotcha
Give me a min
Will do the honours
EDIT
https://drive.google.com/file/d/0B21rpre8LhJ6UXZMQzZHSjNySTQ/edit?usp=sharing
original FW 4.1.2
Click to expand...
Click to collapse
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m
moonbutt74 said:
e.r.,
okay so it's what skyelm said you see the differences?
so now we need a t211 owner with ORIGINAL FIRMWARE to dump their boot loaders and post them.
for now your stuck with what you have.
m
Click to expand...
Click to collapse
yea bro
will try that workaround now
lets see what happens
EDIT:
The workaround is working
flashed the zip again just to repeat that boot loop stuff and it happened
then booted to download mode and flashed stock recovery via odin
the tab booted to system and everything was fine
then did the workaround to flash the deodexed zip i created
and it worked pretty well
Anyone tried flashing the mod ,I mean this:
http://forum.xda-developers.com/gal...7/rom-stock-nf5-lite-rooted-deodexed-t2808633
Over the stock ROM of 4.4,Any boot loops again with the custom recoveries??
Related
One of the AT&T users flashed my ROM on the T-Mobile side. Initial ROMs we were building were not having radio and we assumed it was because we needed to flash modem.bin and amss.bin so we included that as part of our ROM zip and updater-script. When he flashed my ROM, he overwrote his AT&T modem.bin/amss.bin with our T-Mobile modem.bin/amss.bin (who know they were different?)
I feel bad and want get him a quick fix.
If someone could run the commands to pull these files for me and send them via DropBox or whatever so I can make a flashable zip to fix his radio signal, I'd greatly appreciate it.
In terminal emulator (or adb shell in cmd window)
su
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096
Pulls modem.bin
Code:
dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin bs=4096
Pulls amss.bin (if that doesn't work its 0p12 but I'm pretty sure it's 13)
They'll be dumped to your sdcard.
Thank you for any help.
Link's not live yet but when it's done it'll be there. I can upload the other one too.
EDIT: Uploading a zipped one instead - https://dl.dropbox.com/u/40864263/modem.zip
snotyak said:
Uploading the modem.bin here now - https://dl.dropbox.com/u/40864263/modem.bin
Link's not live yet but when it's done it'll be there. I can upload the other one too.
Click to expand...
Click to collapse
Thanks bro
NP. It's live now and the compressed amss.zip should be live in a little bit - https://dl.dropbox.com/u/40864263/amss.zip
snotyak said:
Link's not live yet but when it's done it'll be there. I can upload the other one too.
EDIT: Uploading a zipped one instead - https://dl.dropbox.com/u/40864263/modem.zip
Click to expand...
Click to collapse
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
I have:
Code:
ui_print("Flashing modem ...");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p1", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
ui_print("Flashing amss.bin");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("amss.bin", "/tmp/amss.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p12", "/tmp/amss.bin"),
delete("/tmp/flash_image"));
ui_print("amss.bin Flash complete!");
ui_print("Clearing temp files...");
assert(delete("/tmp/amss.bin"));
delete("/tmp/flash_image");
unmount("/system");
ui_print(" ");
uoY_redruM said:
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
Click to expand...
Click to collapse
It's just a compressed .BIN because it was like 60MB and my internet is slow, haha. I didn't do anything to make it flashable.
Also, see my post above for the amss.bin (also a compressed zip)
uoY_redruM said:
Is it flashable by chance?
I don't have a ton of experience making flashable zips. I have the command lines for it, but I'm not sure how to get the update-binaries? (are they need for flashing something like this?) or the rest of the command lines for the updater-script.
I have:
Code:
ui_print("Flashing modem ...");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing modem...");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p1", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
ui_print("Flashing amss.bin");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("amss.bin", "/tmp/amss.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p12", "/tmp/amss.bin"),
delete("/tmp/flash_image"));
ui_print("amss.bin Flash complete!");
ui_print("Clearing temp files...");
assert(delete("/tmp/amss.bin"));
delete("/tmp/flash_image");
unmount("/system");
ui_print(" ");
Click to expand...
Click to collapse
Could i just insert these into the current att rom in running? Like goto system and put this in the build?
is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt
doh.... :facepalm:
howtomen said:
is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt
Click to expand...
Click to collapse
Like a dumb a$$ i flashed a tmo rom to see if it would wrk. i didnt know that the modem.bin would be in the rom, and now i have no radio. Im trying to get a bin i can use to get my radio back. I looked in the skyrocket forum and saw that people made flashable zips of the radios for this reason, so now thats what im trying to get done. do you know how? Cuz im starting o get worried now.
howtomen said:
is its 60 mb thats not a modem.bin.... what the hell did u people doo....... ****tt
Click to expand...
Click to collapse
hmm, it was pulled from the modem partition with the command line to pull modem.bin. The modem.bin we pulled on our end was 60MB.
It caused absolutely no issues on our end....
kydkupa said:
Like a dumb a$$ i flashed a tmo rom to see if it would wrk. i didnt know that the modem.bin would be in the rom, and now i have no radio. Im trying to get a bin i can use to get my radio back. I looked in the skyrocket forum and saw that people made flashable zips of the radios for this reason, so now thats what im trying to get done. do you know how? Cuz im starting o get worried now.
Click to expand...
Click to collapse
we dont even know where the radio partition is and its not mmcblk0p1 so that means u didnt flash a radio who knows what u flashed which is why i am worried because now not only u but a bunch of tmobile folks have some wierd **** going down there phones....
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
uoY_redruM said:
hmm, it was pulled from the modem partition with the command line to pull modem.bin. The modem.bin we pulled on our end was 60MB.
It caused absolutely no issues on our end....
Click to expand...
Click to collapse
thats cuz its ur device but its not a modem... no way in hell its a modem... who said it was mmcblk0p1?
howtomen said:
we dont even know where the radio partition is and its not mmcblk0p1 so that means u didnt flash a radio who knows what u flashed which is why i am worried because now not only u but a bunch of tmobile folks have some wierd **** going down there phones....
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
thats cuz its ur device but its not a modem... no way in hell its a modem... who said it was mmcblk0p1?
Click to expand...
Click to collapse
Who's having issues with their phone on the T-Mobile end? I haven't heard of anybody at all. This is the first issue I've seen with my ROM other then WiFi Calling not working properly....
As for mmcblk0p1, I can't remember the exact adb shell commands we ran off the top of my head but we found each and every partition using the command and made a list of them all.
Code:
mmcblk0p1 61440 MODEM
mmcblk0p2 128 SB12
mmcblk0p3 256 SB12
mmcblk0p4 512 SB13
mmcblk0p5 2048 aboot
mmcblk0p6 512 rpm
mmcblk0p7 10240 boot
mmcblk0p8 512 t2
mmcblk0p9 512 pad
mmcblk0p10 10240 param
mmcblk0p11 13952 efs
mmcblk0p12 3072 modemst1
mmcblk0p13 3072 modemst2
mmcblk0p14 1536000 system
mmcblk0p15 12832768 userdata
mmcblk0p16 8192 persist
mmcblk0p17 860160 cache
mmcblk0p18 10240 recovery
mmcblk0p19 10240 fota
mmcblk0p20 6144 backup
mmcblk0p21 3072 fsg
mmcblk0p22 8 ssd
mmcblk0p23 5120 grow
mmcblk0boot1 2048 disk
mmcblk0boot0 2048 disk
uoY_redruM said:
Who's having issues with their phone on the T-Mobile end? I haven't heard of anybody at all. This is the first issue I've seen with my ROM other then WiFi Calling not working properly....
As for mmcblk0p1, I can't remember the exact adb shell commands we ran off the top of my head but we found each and every partition using the command and made a list of them all.
Code:
mmcblk0p1 61440 MODEM
mmcblk0p2 128 SB12
mmcblk0p3 256 SB12
mmcblk0p4 512 SB13
mmcblk0p5 2048 aboot
mmcblk0p6 512 rpm
mmcblk0p7 10240 boot
mmcblk0p8 512 t2
mmcblk0p9 512 pad
mmcblk0p10 10240 param
mmcblk0p11 13952 efs
mmcblk0p12 3072 modemst1
mmcblk0p13 3072 modemst2
mmcblk0p14 1536000 system
mmcblk0p15 12832768 userdata
mmcblk0p16 8192 persist
mmcblk0p17 860160 cache
mmcblk0p18 10240 recovery
mmcblk0p19 10240 fota
mmcblk0p20 6144 backup
mmcblk0p21 3072 fsg
mmcblk0p22 8 ssd
mmcblk0p23 5120 grow
mmcblk0boot1 2048 disk
mmcblk0boot0 2048 disk
Click to expand...
Click to collapse
thats not true... you guys pulled that straight from i9300 i remember correcting ur mount points in original updater... u cant find out what mount points are from adb.... and as for modem thats wrong... u can look in ur recovery if u decompile it... infact most of those are i9300 values which no one should use for reference because the devices arent identical inside much less kernel recovery or firmware wise....
howtomen said:
thats not true... you guys pulled that straight from i9300 i remember correcting ur mount points in original updater... u cant find out what mount points are from adb.... and as for modem thats wrong... u can look in ur recovery if u decompile it... infact most of those are i9300 values which no one should use for reference because the devices arent identical inside much less kernel recovery or firmware wise....
Click to expand...
Click to collapse
I literally pulled non of those from i9300. If I could find the commands I ran, I'd show you what I mean. It was something | find "system" and I did "system" "boot" and a few others and it listed the block with block number.
When Five gets on tomorrow, he can confirm. We both found these separately, non of them were found using any reference to i9300.
Alright ladies, play nice.
Sent from my SAMSUNG-SGH-I747 using xda premium
uoY_redruM said:
I literally pulled non of those from i9300. If I could find the commands I ran, I'd show you what I mean. It was something | find "system" and I did "system" "boot" and a few others and it listed the block with block number.
When Five gets on tomorrow, he can confirm. We both found these separately, non of them were found using any reference to i9300.
Click to expand...
Click to collapse
That's wierd because why would u get I9300 modem partition and its not ours....
Sent from my HTC Desire HD using xda premium
I'm able to get signal now but it's only edge and 3g. So I guess it's on tmo but all my phone info says att. What should I do to get to lte and hspa+? I have the right apn too.
Sent from my SAMSUNG-SGH-I747 using xda premium
howtomen said:
That's wierd because why would u get I9300 modem partition and its not ours....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
The modem.bin and amss.bin I uploaded for him/them were from your ROM....??
Disregard this if you're talking about something completely different
snotyak said:
The modem.bin and amss.bin I uploaded for him/them were from your ROM....??
Disregard this if you're talking about something completely different
Click to expand...
Click to collapse
No itll work to.fix that dudes stuff but its not what it seems
Sent from my HTC Desire HD using xda premium
Has anyone created a clockworkmod for this? This phone can be rooted, thru two apps, poot, and ministro(Qt). It still has gingerbread 2.3.6, and I need clockworkmod, or the source code, to use clockworkmod's builder. It is the cdma variant of the alcatel 995(which is gsm). can anyone point me in the right direction?
Source Code
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
reggjoo said:
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
Click to expand...
Click to collapse
how did you get it rooted?
rooting alcatel authority (960c)
squidbutt said:
how did you get it rooted?
Click to expand...
Click to collapse
First make sure you have USB Debugging checked and your allowing instalation of unknown sources
DL these from the play store:
Minstro2
Superuser
DL poot.apk: View attachment poot.zip
Run poot, click yes to download the extra librarys, click "click here to poot" you will need to restart the phone when it prompts. You should be rooted now :good:
You can DL ES File Explorer(from play store) and in the settings check: Root Explorer, Up to Root and Mount File System. Now you can manage all the files on your phone but be careful of what you delete, some of the stock apk's are very hard to recover if you delete them.
Hope this helps
Download superuser first
Download superuser first, you won't be able to run it until the phone's rooted. after it's rooted, it will work. This way, seems to stop a problem, when you go thru the steps to root. Some people had a error. If you plan to open the /data, /system, or dalvik cache, on your computer, install chainfire's adb insecure. These folders don't open without this, on a computer.
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Haven't seen this
aldude999 said:
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Click to expand...
Click to collapse
Hello, I haven't looked into this thread for a while. I see that you have some info for these blocks. that I couldn't get. I tried using root explorer, to look into some files, and they couldn't load, and tried to use too much memory, just to attempt to open, which, my phone said it was low on memory. Hate gingerbread, and kwansi choi( maker of this rom), This phone could easily handle a later os.
The usb ID's, are "Device 007: ID 1bbb:9018" .
USB ID's
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
reggjoo said:
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
Click to expand...
Click to collapse
I noticed that:
mmcblk0p15
mmcblk0p12
mmcblk0p8
all have the same number of blocks.
The FOTA code shows
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
Click to expand...
Click to collapse
applypatch useage is as follows:
applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Click to expand...
Click to collapse
Apply patch from blk8 to blk15.
So maybe I was mistaken with what I thought was the partition. Blk8 seems to be where fota grabs it's updated partition from?
This shows that blk15 may actually be the recovery partition. Still useless unless the bootloader can be worked on.
Battery terminals
As we know, if the battery is out, the phone will do nothing( unlike my old huawei, it didn't matter). I wondered if that was the reason why, it's so hard to unlock it. I think the bootloader has been set up to not respond to attempts. The bootloader condition treats the phone as if there's no power to it(?) . I found out that the middle terminals, of the battery contacts, will power the phone, if they're connected, but only for a few seconds.
Maybe there's some code that's unknown, or procedure. The phone doesn't respond to fastboot commands, and I can't enable it(function), on it. In the default.prop file, I see that ro.secure, is 1. Whenever I try to change it to 0( in rewritable mode), it never takes. So this is a little info.
reggjoo said:
The bootloader condition treats the phone as if there's no power to it(?)
Click to expand...
Click to collapse
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
aldude999 said:
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
Click to expand...
Click to collapse
Yes, I think alcatel's a little shady. I use a dual boot pc, and I found out, using the lsusb command, that the usb id's were different, than what the id's were for the supposedly official usb drivers. Sent them a msg, and they said I was wrong( can't be wrong if everything works!). They take no responsibility for their hardware, and I let people know, every chance I get, whenever I see a review of a phone from them. I found out the id's were wrong, when, before I even rooted it, I installed their onetouchmanager, and it couldn't find my phone( what! out the box!). That's not the way you do things.
Bringing 960C Back To Life!!!
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
thealexday said:
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
Click to expand...
Click to collapse
I still am using my 960c. I wouldn't mind finding the original stock rom or finding out how to upgrade to a newer android version. Currently running version 2.3.6
Too bad I don't know much about modding save for rooting and flashing. I gather there are still some of us here who really like our 960c phones otherwise.
Hey guys! I am in deep trouble (or so I think). I just came back from my Winter vacation but sadly I left my Note 3 behind at my brother's house. I won't be getting it back anytime soon (literally) so I'm back to using the Galaxy S3 as my main phone. Though I wasn't using the S3 as my main phone, I still kept it up to date with the new things (Gummy 4.4.2 with the newest CWM and Ktoonsez (12.20.13 release)).
My problem relies here when I decided to flash a new ROM and tried entering my recovery and got slapped with an Android with a loading bar. It quickly rebooted my phone back and I thought, "CWM is notorious when it comes to issues" and so I went on and flashed TWRP 2.6.3.1 through GooManager. I rebooted into recovery and got slapped again but this time, it was telling me this: "Running OpenRecoveryScript... Installing Zip" follow by an "E:" error. These were the E: errors I was getting:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
I've tried reinstalling the recovery numerous amount of times just to be presented with the same error.
My instincts tells me to Odin back to full stock so it would repartition the recovery but my curiousity asks me, "What if you can't go into the recovery to factory reset in order to boot into the Android firmware?" That would only mean I would be stuck with a phone that hangs in the Samsung logo screen.
I've also discovered that my root cache folder (Cache Partition or so I think) is completely empty (apparently, that's where the recovery folder is suppose to be and such) but for some odd reason, my phone is fully functional (apps, texts, phone calls, etc..) with the exception of entering Recovery Mode.
What should I do before making any kind of moves (my phone is fully functional with the exception of entering recovery mode)?
Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.
Perseus71 said:
Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.
Click to expand...
Click to collapse
Thank you for taking the time to read and respond to my question
I'll try doing that and see if it'll work. I've tried installing TWRP through Terminal Emulator and used the this command to push the recovery into the mmcblk0p18 (recovery partition):
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Sadly it didn't work but I will try using your method and see where it'll go.
With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.
Perseus71 said:
With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.
Click to expand...
Click to collapse
It didn't work. One thing I've noticed is that the CWM logo (Samsung logo with the CM alien) pops up before TWRP which makes me thing CWM has something to do with it.
This is the Odin process when I tried to Odin the recovery:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I also used this file to install the recovery:
openrecovery-twrp-2.6.3.1-d2tmo.tar
I took a screenshot of the partitions using diskinfo. Do you see anything wrong with any of the partitions?
That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.
Perseus71 said:
That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.
Click to expand...
Click to collapse
It still gives me these two errors before rebooting me back into Andriod:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.
Perseus71 said:
Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.
Click to expand...
Click to collapse
Are you sure it's safe to Odin back to stock despite the fact I can't enter recovery mode? My plan was to Odin stock but sometimes in order to boot into android, you must go into recovery mode and do a factory reset. It's the reason why I ask if it's safe to Odin back to stock (root or no root?).
By the way, thank you again for taking your time out to help me
Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.
Perseus71 said:
Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.
Click to expand...
Click to collapse
For some odd reason, when I press 'Erase Everything', it doesn't do anything. Maybe it's because I'm using a 4.4.2 nightly from Gummy. Is there another way to factory reset besides entering Recovery and Factory Reset from phone?
There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)
Perseus71 said:
There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)
Click to expand...
Click to collapse
In other words, I should uncheck A.Reboot (Auto Reboot) when I Odin back to Stock?
You got it.
Perseus71 said:
You got it.
Click to expand...
Click to collapse
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?
Noobiologist said:
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?
Click to expand...
Click to collapse
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
su
reboot nvbackup
Click to expand...
Click to collapse
It helps if you happen to loose your IMEI in future at some point.
Perseus71 said:
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
It helps if you happen to loose your IMEI in future at some point.
Click to expand...
Click to collapse
Thank you for the input! I believe I have a backup of my EFS partition in my SD Card (had it there since SGS3 was still running ICS) but I will do it again once I Odin the phone. What I'm really starting to believe is the PIT is probably messed up. What I need to confirm this is someone who has a SGS3 (T-Mobile 16GB) to download and run diskinfo from the Play Store and check the total size of the Cache Partition (mmcblk0p17) and/or download and run Terminal Emulator with these command prompts:
PHP:
su
cat /proc/partitions
This is what I got when I used the commands:
PHP:
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 32 15558144 mmcblk1
179 33 15557120 mmcblk1p1
254 0 2110 dm-0
I could use this as a way to see if my PIT matches with a fully functional SGS3 (T-Mobile 16GB).
I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.
Perseus71 said:
I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.
Click to expand...
Click to collapse
That's a good thing! That means my PIT (theoretically) is fine. The reason why I asked for the diskinfo is to check the total space of the Cache Partition (Mine shows 826MB of total space). My ultimate theory is of course whether the firmware would actually do something about my Cache Partition (since it seems like the only reason my recovery isn't working is due to the fact it's not retrieving the information that's supposibly should be in the Cache Partition (E: TWFunc: : Copy_Log -- Can't open destination log and E: Unable to open '/cache/recovery/.version')).
It seems to me that the Cache Partition isn't writing the necessary files from the recovery image hence the fear of not being able to enter Stock Recovery to Format Data resulting in a boot-loop.
If you have a root file explorer, could you check the /Cache found in your root to see if you have any content there or something like a recovery folder in it?
Thanks
I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.
RUU should fix it as long as you can get to bootloader.
RUU
yourunlikegus said:
I have two Verizon HTC Ones (silver and blue) I recently was looking around and saw all the "convert your HTC one to developer/gpe edition" talk and thought, "why not." I figured everything was okay and didn't do as much reading as I normally do. I changed the MID (had SuperMID from java card s-off) to developer edition and, flashed GPE firmware then tried flashing RUUs and when that wouldn't work tried a ROM (Android Revolution HD 5.1). Well, obviously none of this is compatible with a Verizon HTC One and there are now.......issues. As, i said, both of the phones were s-off via java card. Now the silver is S-on, there is no hboot. I can flash recovery, flash roms, etc (they won't boot). But cant figure out how to flash firmware/hboot with s-on. I am using the Blue variant now with Insertcoin ROM and it is great. but the Blue suffers from a severe case of the "pink camera." whereas the silver does not. Is there anyway to fix this or is it bricked. Attached a few pics of the devastation.
Click to expand...
Click to collapse
Have you tried to boot into RUU just to see what happens??
lj50036 said:
Have you tried to boot into RUU just to see what happens??
Click to expand...
Click to collapse
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Feedback
yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Have you tried flashing the firmware in post 2 ??
yourunlikegus said:
I can get into RUU. I haven't found an exe so have been trying .zip (there is probably an exe staring me in the face but damned if I can find it). The problem is I changed my MID to developer edition and I'm not sure if that's affecting it or not. Been using both signed and not zips from http://forum.xda-developers.com/showthread.php?t=2485319 Just hangs at parsing index or errors out. I really hope I'm missing something obvious. See attached pic
Click to expand...
Click to collapse
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours
lj50036 said:
Have you tried flashing the firmware in post 2 ??
Click to expand...
Click to collapse
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid
Hang Tight
yourunlikegus said:
From the thread I posted? yes...hangs at parsing index. The .zip i can open is a bunch of .img files. the rest i cant open, says they are invalid
Click to expand...
Click to collapse
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....
lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
Click to expand...
Click to collapse
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.
BD619 said:
Are you unzipping the signed zips? There may be a .exe inside
If you are using the cmd window to flash you should be able to flash the decrypted RUU
Edit check the Sprint RUU thread see if your RUU is setup like ours
Click to expand...
Click to collapse
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.
yourunlikegus said:
Yeah, I've tried both and it either hangs or errors out. Attached is shot of flashing firmware...just sits there at that point.
Click to expand...
Click to collapse
Give me a list of all the .img files that you see from the firmware zip
I think I have a solution maybe.. With the bootloader unlocked we can still us fastboot not RUU... We will just have to flash them from fastboot one at a time... give me a list I will work on it....
lj50036 said:
Ok I am looking into some things give me a sec......
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
So you have tried both the RUU and the firmware zips???
---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------
List all the .img files here so I can see what is there.....
Click to expand...
Click to collapse
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps
yourunlikegus said:
Well, I can't open the signed zips that are for the vzw (says windows cant, invalid) but I can open 1 of the developer edition ruus that i have...not sure if that really helps
Click to expand...
Click to collapse
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
yourunlikegus said:
Will download and attempt it but I'm pretty sure the sprint stuff will be incompatible too. When I tried to run the developer edition ruu.exe it said connection error, plug usb cable in, etc. (not sure of exact error code)
And after succesfully botting into RUU, after the failed attempts and hangs, I cannot fastboot reboot-bootloader, that just hangs too. I have to hold the power button down.
Click to expand...
Click to collapse
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
You can't flash older firmware or RUUs if you are s-on
BD619 said:
What I mean is check your RUU and see if it's setup the same as Sprint not flash it
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
You can't flash older firmware or RUUs if you are s-on
Click to expand...
Click to collapse
ok. I'll have to figure out which one is hboot 1.54
yourunlikegus said:
ah, was in the middle of posting. here is the 1.10.605.10_firmware.zip firmware files :
android-info.txt
boot.img
hboot_signedbyaa.img
radio.img
text from android-info in attached pic. I went with the oldest firmware on the page because i am going to s-off once/if this gets fixed and didn't want any issues
Click to expand...
Click to collapse
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know
lj50036 said:
On that forum did you try to get one of those RUU and upack it?? A newer one like 2.10.605.1 decypted???
2.10.605.1 is hboot 1.54 for sure try to flash that one from RUU just so we know
Click to expand...
Click to collapse
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol
Pic of files in 2.10.605.1 firmware.zip
Partition Table
yourunlikegus said:
Downloading both ruu and firmware for 2.10.605.1. Will flash soon and see what happens. i think i have tried this one already but i can't remember lol
Click to expand...
Click to collapse
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...
lj50036 said:
Code:
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1 sbl1
179 2 256 mmcblk0p2 sbl2
179 3 130671 mmcblk0p3 pg1fs
179 4 1 mmcblk0p4 ?
179 5 16 mmcblk0p5 board_info
179 6 256 mmcblk0p6 mfg
179 7 15577 mmcblk0p7 pg2fs
179 8 256 mmcblk0p8 sbl2_update
179 9 1024 mmcblk0p9 sbl3
179 10 256 mmcblk0p10 rpm
179 11 2048 mmcblk0p11 tz
179 12 2080 mmcblk0p12 hboot
179 13 5120 mmcblk0p13 sp1
179 14 1024 mmcblk0p14 wifi
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23 debug_config
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25 control
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 98727 mmcblk0p29 reserve
179 30 54270 mmcblk0p30 reserve_2
179 31 76800 mmcblk0p31 radio
179 32 98303 mmcblk0p32 ?
179 33 16384 mmcblk0p33 boot
179 34 16383 mmcblk0p34 recovery
179 35 1900543 mmcblk0p35 system
179 36 655359 mmcblk0p36 cache
179 37 27262976 mmcblk0p37 userdata
Here is a list of the partitions... If you were to match up the img with the partition, Im sure you would be able to flash from fastboot
An example of a command work be like this
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
This is just an example.... I would have no idea in which order you would want to flash them...
Click to expand...
Click to collapse
wont let me erase...remote not allowed. I was able to flash boot, but so far everything else i try is failed remote not allowed also for rcdata and adsp get signature verify fail
I don't know if this is the is the correct place to post this, but here goes...
I have noted in various nexus 7 forums that quite a few people can't flash a rooted Lollipop beacause for whatever reason they have no access to a PC.
I've posted how to get around this, but I know how difficult searching forums for specific information can be.
So, if enough people out there need a step by step guide, I will post it here...
Show me how
I would like to know too...
Sent from my SM-N900V using XDA Free mobile app
Flashing the new bootloader is the problem for me....
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Yeah we kinda have to wait for a recovery flashable bootloader 4.04 still
Same here, just need to be able to flash that bootloader and I'm good from there. Thanks for the effort.
Sent from my Nexus 7 using Tapatalk
Would love a flashable zip as well...I have no PC access but have a bl unlocked n7
Same for me. All I need is a flashable zip for the new bootloader.
Same here.
Sent from my Nexus 7 using Tapatalk
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or something?
I assume this is where I should be if I'm looking to update my rooted N7, which has no working USB port (I charge on a QI charger).
Is this promising or am I stuck on KitKat?
Thanks!
Well you should be able to flash to Lollipop as soon as we have a recovery flashable bootloader.zip
Some seem to have flashed the latest ROM without the 4.04 bootloader but I am not sure they still have working root and some other issues.
I have tried to extract the files needed to make the flashable bootloader but am having trouble, so it could be the reason we don't see one yet.
Someone smarter than myself in these matters may have more insight. But so far I have not heard anything from anyone else that has attempted to make a flashable bootloader for 4.04
PsychoMcSatan said:
I assume this is where I should be if I'm looking to update my rooted N7, which has no working USB port (I charge on a QI charger).
Is this promising or am I stuck on KitKat?
Thanks!
Click to expand...
Click to collapse
I saw several posts were people did not update to 4.04 and did not seem to have any trouble, so I decided to try myself, I put a copy of the pre-rooted rom in my downloads
I made a backup, did a factory reset, installed the rom, rebooted and, installed the titanium backup on their twitter feed, restored, and everything seems to working just fine.
I am not sure what the bootloader does affect in the end as far as the running OS goes(not sure why it would affect that), I will upgrade it, if I get a flashable one, but for now I seem to be running Lollipop ok.
kernelsandirs said:
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or something?
Click to expand...
Click to collapse
I am trying ImgRePackerRK and i am getting 'unknown header formant'
im in cmd.exe. i type: Imgerpackerrk.exe bootloader-flo-flo-04.04.img
I put everything in the same folder to make the typing the syntax faster. Is that the same error you are getting?
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
2014.11.13 22:59:27 imgRePackerRK (v. 1.04 windows)
2014.11.13 22:59:27 (c) RedScorpio, Moscow, 2013-2014
2014.11.13 22:59:27
2014.11.13 22:59:27 Command parameters: "/log" "bootloader-flo-flo-04.04.img"
2014.11.13 22:59:27
2014.11.13 22:59:27 Run parameters:
2014.11.13 22:59:27 log = 1
2014.11.13 22:59:27 debug = 0
2014.11.13 22:59:27 quiet = 0
2014.11.13 22:59:27 mono = 0
2014.11.13 22:59:27 md5 = 0
2014.11.13 22:59:27 rkcrc = 0
2014.11.13 22:59:27 rkaf = 0
2014.11.13 22:59:27 skip = 0
2014.11.13 22:59:27 2nd = 0
2014.11.13 22:59:27 cid = 0
2014.11.13 22:59:27 memsize = 134217728
2014.11.13 22:59:27
2014.11.13 22:59:27 ==========================[ START ]==========================
2014.11.13 22:59:27
2014.11.13 22:59:27 --- Firmware unpacking ---
2014.11.13 22:59:27
2014.11.13 22:59:27 2-nd layer file unpacking
2014.11.13 22:59:27 RockChip bootloader image format detected
2014.11.13 22:59:27 "bootloader-flo-flo-04.04.img" (RockChip bootloader image) unpacking
2014.11.13 22:59:28 Image properties:
2014.11.13 22:59:28 Type RockChip bootloader image (BOOT)
2014.11.13 22:59:28 Version 21.52
2014.11.13 22:59:28 Date 0.00.21
2014.11.13 22:59:28 Time 61:00:115
2014.11.13 22:59:28 ChipID 0x00316c62
2014.11.13 22:59:28 Code(?) 0x02000000
2014.11.13 22:59:28
2014.11.13 22:59:28 .ERROR. Unknown header format
2014.11.13 22:59:28
2014.11.13 22:59:28 ==========================[ STOP ]==========================
Here is the full description
You can extract the factory image tar gunzip with https://play.google.com/store/apps/details?id=com.rarlab.rar&hl=en
it's alot easier then using windows tools.
Flashify allows you to flash boot and recovery images, I don't see why a extra option couldn't be added for flashing the bootloader also.
If you knew which block the bootloader was stored you could flash it with a terminal emulator also.
The only one I know is
dd if=system.img of=/dev/block/mmcblk0p22
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 34335 loop0
179 0 15388672 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 13029359 mmcblk0p30
254 0 34335 dm-0
[email protected]:/ #
So it looks like we have the bootloader here: http://forum.xda-developers.com/showpost.php?p=56737284&postcount=12
But I want to make sure I do things in the right order. I have no USB port on my rooted N7 (2013). So I thought I'd go ahead and flash the ROM via TWRP as people have had success with the old bootloader. After that I can flash the bootloader to be nice and up to date? Will that mean I lose root at that point? If so, how do I reroot over WIFI?
Thanks!
If you flash the rom from http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx21p-t2938161 it is pre rooted i just downloaded it to my device, rebooted to twrp, made a backup, factory reset, install that rom and rebooted. Worked great. Also Eksasol posted the recovery flashable bootloader here
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/ get the bootloader one from the link. thanks @eksasol
PsychoMcSatan said:
So it looks like we have the bootloader here: http://forum.xda-developers.com/showpost.php?p=56737284&postcount=12
But I want to make sure I do things in the right order. I have no USB port on my rooted N7 (2013). So I thought I'd go ahead and flash the ROM via TWRP as people have had success with the old bootloader. After that I can flash the bootloader to be nice and up to date? Will that mean I lose root at that point? If so, how do I reroot over WIFI?
Thanks!
Click to expand...
Click to collapse
dilfatx said:
Show me how
Click to expand...
Click to collapse
I've just discovered where my original post was moved to.
So if anyone still wants to know how to get lollipop without the latest bootloader, let me know.
I assume after a couple of weeks this has been solved, but if not...
Cheers...
SHABBYLEA said:
I've just discovered where my original post was moved to.
So if anyone still wants to know how to get lollipop without the latest bootloader, let me know.
I assume after a couple of weeks this has been solved, but if not...
Cheers...
Click to expand...
Click to collapse
This was a great trouble for me back then,hell I didn't discovered your thread that time and I'd had to beg for a PC,I sold my PC some months ago!
Thanks @Q8-VO8 liked the trick!