Just got my new sgs2 from germany
Already got the cm tough case, its good but hard to remove when needed.
As a n00b with the I9100, few things:
1. From my older I897 I know COG roms, is it the better option here too?
2. What way should I root my device? I know there is normal root and cf root
For unlocking I know there is chainfires app
Anything else I need to know?
Sent from my SGH-I897 using XDA App
Be useful to know about the rootin too please
easiest way
iakovl said:
Just got my new sgs2 from germany
Already got the cm tough case, its good but hard to remove when needed.
As a n00b with the I9100, few things:
1. From my older I897 I know COG roms, is it the better option here too?
2. What way should I root my device? I know there is normal root and cf root
For unlocking I know there is chainfires app
Anything else I need to know?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Well for me, I looked at the available ROMs and evaluated how troublesome each was flashing. And started from the easiest one to flash. I have not tried any other.
I read about 2 weeks in diffrent android forums before I flashed new ROM. It isn`t very dificult but at the moment there is simply no need to flash a custom ROM. There are very slight performance increases. But this will be different in 1 month I guess.
The ROM Guys here are very motivated! They ll do great work
To root, I flashed CF-Root kernel from this post:
http://forum.xda-developers.com/showthread.php?t=1103399
Very easy to do. Many thanks to Chainfire.
allanon+ said:
To root, I flashed CF-Root kernel from this post:
http://forum.xda-developers.com/showthread.php?t=1103399
Very easy to do. Many thanks to Chainfire.
Click to expand...
Click to collapse
I get root and a custom ROM in the same amout of process
Could anyone tell me which Kernel to put on?
I presume its 4.1 as thats the latest?
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 11836 views)
CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 14348 views)
CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 4533 views)
CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 41211 views)
CF-Root-SGS2_XX_OXA_KF2-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 18589 views)
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 6970 views)
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4.zip - [Click for QR Code] (5.98 MB, 4642 views)
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip - [Click for QR Code] (6.08 MB, 9980 views)
I have an orange branded S2S with BVKE2 firmware on now?
Any help appreciated before I install it!
Funkyfin2000 said:
Could anyone tell me which Kernel to put on?
I presume its 4.1 as thats the latest?
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 11836 views)
CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 14348 views)
CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 4533 views)
CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 41211 views)
CF-Root-SGS2_XX_OXA_KF2-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 18589 views)
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 6970 views)
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4.zip - [Click for QR Code] (5.98 MB, 4642 views)
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip - [Click for QR Code] (6.08 MB, 9980 views)
I have an orange branded S2S with BVKE2 firmware on now?
Any help appreciated before I install it!
Click to expand...
Click to collapse
I believe that the KG1 is the kernel being used in 2.3.4 roms. And the KF2 has newer modems than KF3 (old modem). And I'm unsure of KF4.
So do i need to upgrade to 2.3.4 first?
Orange has no update avaialble for 2.3.4 so guess I need to put that ROM on from somewhere? But I thought i couldn't do that before I rooted?
Ive come from a hero you see, things are a bit different! @
Funkyfin2000 said:
So do i need to upgrade to 2.3.4 first?
Orange has no update avaialble for 2.3.4 so guess I need to put that ROM on from somewhere? But I thought i couldn't do that before I rooted?
Ive come from a hero you see, things are a bit different! @
Click to expand...
Click to collapse
Well, in my case I just flashed Lite'ning rom which comes with root. So you only need 1 file to flash. This was when it was version 1.5. Now you have to flash 2.0 via odin and then flash the 2.1 update via CWM as I recall. I am not really sure about other processes since I have not tried others. Anyway, I hope this helps you somewhat.
You should always flash stock aim version (2.3.4) if the version is different (2.3.3. -> 2.3.4) to prevent any issues with the new rom. The new version is a 3file packet an data will be wiped.
You would need root first if you need to backup eg with titanium.
Related
Hey all,
I've been looking into how QDLTool works a bit and figured out how to swap the images that it flashes. Please note that QDLTool verifies image hashes for a good reason. You should understand the risks before attempting to meddle with QDLTool for any reason. Anything you do is at your own risk.
I would *strongly* recommend not flashing anything but amss, system, recovery and boot from any custom builds. Any time you flash a partition image, dbl, fsbl or osbl, you run the risk of bricking your device beyond recovery.
Important note: The information below is based entirely on analysis of QDLTool. I haven't used this to flash an image yet. If you plan on using this for development, you'll have to take that step.
Let's get to the details:
QDLTool automatically determines what to flash from the images/ directory. It stores a hash internally for each of the files that it will flash. This hash is basically just a 32-bit XOR of the bytes in the file:
Code:
#!/usr/bin/python
import sys
x = open(sys.argv[1], "rb").read()
print "%02x%02x%02x%02x" % (reduce(lambda x,y: x^ord(y), x[3::4], 0), reduce(lambda x,y: x^ord(y), x[2::4], 0), reduce(lambda x,y: x^ord(y), x[1::4], 0), reduce(lambda x,y: x^ord(y), x[0::4], 0))
To swap out an image, you need to patch the old hash of a file that was previously flashed with the new hash of the file that you'd like to flash.
For this post, I'll assume you're looking at QDLTool from streakflash.zip with MD5 = 63b64ba6a9d1ee770998d2a0e4a19df1.
In this file, the hashes start at offset 0x5fa90. There are 14 of them:
Code:
0005fa90 0b b0 a7 5c 3e e9 bb 29 17 4e 8d ac a0 dc 43 62
0005faa0 2c 3f 4e f1 fb 6b fc 80 11 9d 22 07 66 70 22 4a
0005fab0 bc 38 64 95 d2 c6 72 29 6d f8 99 e2 cc 74 14 49
0005fac0 1b ad 7a 9c 77 fb ee cc
As 32-bit words, they are:
5CA7B00B
29BBE93E
... etc ...
9C7AAD1B
CCEEFB77
In order, they are:
00. Partition (hash = 5CA7B00B)
04. Dbl (hash = 29BBE93E)
08. Fsbl
0c. Osbl
10. Amss
14. Dsp1
18. DT
1c. Appsbl
20. Boot
24. System
28. Userdata
2c. Recovery
30. Logfilter
34. RCFile
So, if I wanted to flash a new recovery, I'd take the hash of my recovery file via the Python script above, then replace the bytes at 0x5fa90 + 2c = 0x5fabc with my hash (stored in little-endian, of course).
It's a bit of manual work at this point, but I think a lot of this could be automated. You'd probably be better off and safer using batch files and fastboot though.
we discovered batch files to flash the images is a bad idea as some images cant be flashed using the normal fastboot mode
Thanks,
i'am looking some infomation about QDLTool also.
but i've no idea what hash was
i'll probatly wait for some "automated" way
QDLTools has so much potention. Somebody that knows coding should make it a automated system for us the little people...
Sent from my Dell Streak using XDA App
Yes, it would be nice if someone could figure out a way to insert new "roms" into the QDL tool, so when new updates are release, it would be a no brainer to do the updates without having to go through a bunch of command lines, or hocus-pokus to get an updated rom (minus the bloated carrier rom) onto the device.
Years ago, I played around with Linux, and found the same issue. A lot of command line knowledge is required. My command line stopped at dos 6.x, going all the way back to dos 2.x
Windows spoiled everyone
Its been very quiet in these forums recently, probably because everyone has bought a Galaxy S2 or a HTC Sensation!
I recently came across UPX, this is a compression utility that can shrink exe and dll files quite dramatically, saving space and increasing application launch speed quite dramatically.
I am currently using Mirom8 and even though this Sense 2021 rom is protected have decided to list exe and dll files that can (I think) be UPXed for speed
Here is a list of exe and dlls from the \windows folder and their UPXed size:
AdjustMotionSensor.exe 109k
AdobeReaderLE.exe 1050k
AlarmPopUp.exe 105k
AlbumSearcher.exe 135k
AudioBooster.exe 87k
AudioManager_Eng.exe 76k
BackupRestoreUI.exe 220k
Camera.exe 161k (nice increase in launch speed here)
CommManager.exe 152k
ConnectionSetup.exe 112k
ConnectionSetupAuto.exe 115k
ContactEditor.exe 66k
EmailSetupWizard.exe 97k
Facebook.exe 206k
HTCAlbum.exe 400k
HTCAppointment.exe 105k
HTCBookmark.exe 123k
HTCDRMEngine.exe 949k
HTCMsgEnhance.exe 110k
HTCPhotoPicker.exe 358k
OneNoteMobile.exe 268k
PPCPimBackup.exe 147k
PPT.EXE 687k
PushClient.exe 137k
PWORD.EXE 128k
PXL.EXE 291k
RSSHub.exe 266k
ServiceMode.exe 160k
SettingImprovement.exe 90k
SIM_MGR.EXE 82k
SimLockP.exe 49k
SimMgr.exe 117k
SPMC.EXE 117k
StreamingPlayer.exe 165k
Uploader.exe 97k
WiFiNetwork.exe 67k
wma9prodecoder.dll 236k
wmv9decoder.dll 258k
WMVDMOE.DLL 238k
YouTube.exe 145k
And other useful savings
Opera 10, 2 largest files can be UPXed, flashlite, the large dll can be UPXed
S2U2, all exe's can be UPXed, makes the unlock screen quite smooth to use
Its not worth UPXing files less that 200k although it might help a slow launching app around the 150k size, and normally its not worth UPXing files that stay resident in ram all the time, as it can use quite a lot more ram than normal, but if you launch apps a lot, then it can really make a difference to the speed of opening your favourite applications. Apps that use .net cannot be UPXed either, so that is a limiation otherwise more files could be UPXed.
Very good work!!! Have you send me all the files? I will over weekend swap the files and re cook mirom8.
mirolg said:
Very good work!!! Have you send me all the files? I will over weekend swap the files and re cook mirom8.
Click to expand...
Click to collapse
Hi Miro
I will send you a rar file again via email today at some point.
This can be done to other rom releases too you know, i am unsure of total rom savings space wise, possibly 20MB-30MB, not huge but we are talking a whole 20MB plus of internal storage free for something else.
Also it would be useful to know whereelse in the rom there are exe files i can try to upx, must be other places.
(InsertNameHere) said:
Its been very quiet in these forums recently, probably because everyone has bought a Galaxy S2 or a HTC Sensation!
Click to expand...
Click to collapse
Yes, it seems that only few person are on the forum. Maybe drupad will show up after return from vacation. It is over
Regards
fxdjacentyfxd
(InsertNameHere) said:
Hi Miro
I will send you a rar file again via email today at some point.
This can be done to other rom releases too you know, i am unsure of total rom savings space wise, possibly 20MB-30MB, not huge but we are talking a whole 20MB plus of internal storage free for something else.
Also it would be useful to know whereelse in the rom there are exe files i can try to upx, must be other places.
Click to expand...
Click to collapse
miROM1 and miROM8 are good ROMs and if we can save 20 - 30 MB Storage, then will be much better! i try it and give you a feedback!
good work, tnx
mirolg said:
miROM1 and miROM8 are good ROMs and if we can save 20 - 30 MB Storage, then will be much better! i try it and give you a feedback!
good work, tnx
Click to expand...
Click to collapse
How about coking this with latest manila u had in mind??
thanks for this!!!
nikola92 said:
How about coking this with latest manila u had in mind??
Click to expand...
Click to collapse
Miro is working on it for us
hi, a short statement:
my sense 2021 package i have compressed with cfc.method the result is sense and sense tabs starts quicker and works really faster. ok. miROM1 and mirom8 are in the lastest relases also fast, but all starts 0,5 sec. quicker. UPX method compress the exe + dll files and the result is from app to app different- but i mean the most works better and we save few MB storage. miROM8 has now 270 MB and miROM1 has 256 MB free Storage.
Both ROMs are with all fixes and updates incl. cam-button and toshiba power + wifi settings.
I would test it and will upload it next days
cheers, miRO
mirolg said:
hi, a short statement:
my sense 2021 package i have compressed with cfc.method the result is sense and sense tabs starts quicker and works really faster. ok. miROM1 and mirom8 are in the lastest relases also fast, but all starts 0,5 sec. quicker. UPX method compress the exe + dll files and the result is from app to app different- but i mean the most works better and we save few MB storage. miROM8 has now 270 MB and miROM1 has 256 MB free Storage.
Both ROMs are with all fixes and updates incl. cam-button and toshiba power + wifi settings.
I would test it and will upload it next days
cheers, miRO
Click to expand...
Click to collapse
Good news and sounds quite exciting, i am glad you found a way to get CFC working with 2021, i had read it was somewhat more difficult than previous versions like 2012, and UPX saves some space, thats good too.
270MB user storage is incredible i would say!
Great job!
Which version of UPX did you use ?
can i have a link ?
lesscro said:
Which version of UPX did you use ?
can i have a link ?
Click to expand...
Click to collapse
Any version above 3.03 supplied with this batch utility works fine, but i used the latest version 3.07
Best to do all compression on your pc rather than use a PPC version, it can take quite a long time to compress a large exe file.
thx for all... i will test myself on my TG !
Actually i tried this files to perform a speed test :
Code:
Explorer.exe 268 288 2010-09-07 20:46 -a---
GoogleMaps.exe 2 354 176 2010-06-25 19:47 -a---
iGo.exe 8 613 376 2011-05-08 09:07 -a---
iManager.exe 356 352 2011-02-21 17:00 -a---
InfoTrafic Trains.exe 319 488 2010-03-17 23:28 -a---
Opera10-armv4i.exe 623 400 2010-03-15 20:48 -a---
PhotoManPro.exe 1 108 480 2010-04-26 16:29 -a---
player.exe 1 894 672 2009-09-17 11:14 -a---
RCapture.exe 90 112 2010-04-26 16:28 -a---
s2p.exe 364 032 2010-07-17 05:35 -a---
SKTools.exe 2 657 208 2010-03-02 15:09 -a---
ThemeChanger.exe 113 912 2007-04-18 07:43 -a---
Weather-iGo-PPC-v2.exe 264 192 2010-11-11 17:49 -a---
And only a few Exe seems to be work like my old test with my P535 long time ago...
it appear too somes EXE manage in .NEt/win32 are not supported actually !
But when it work... it s soooooooooooooooooo fastest !
Working file compression :
Code:
Explorer.exe 252 928 2010-09-07 20:46 -a---
GoogleMaps.exe 855 040 2010-06-25 19:47 -a---
iManager.exe 203 264 2011-02-21 17:00 -a---
Opera10-armv4i.exe 246 568 2010-03-15 20:48 -a---
PhotoManPro.exe 499 712 2010-04-26 16:29 -a---
RCapture.exe 53 248 2010-04-26 16:28 -a---
then i have seen on Mirolg ROM thread you manage a complete suite with standard TG exe... can you share this package, i think system files (*.exe) is universal...
And maybe you win when i will finish my new SKIN in test !
other nice idea to still use this tool always updated... i forgot it ! but it s very usefull !
lesscro said:
Actually i tried this files to perform a speed test :
Code:
Explorer.exe 268 288 2010-09-07 20:46 -a---
GoogleMaps.exe 2 354 176 2010-06-25 19:47 -a---
iGo.exe 8 613 376 2011-05-08 09:07 -a---
iManager.exe 356 352 2011-02-21 17:00 -a---
InfoTrafic Trains.exe 319 488 2010-03-17 23:28 -a---
Opera10-armv4i.exe 623 400 2010-03-15 20:48 -a---
PhotoManPro.exe 1 108 480 2010-04-26 16:29 -a---
player.exe 1 894 672 2009-09-17 11:14 -a---
RCapture.exe 90 112 2010-04-26 16:28 -a---
s2p.exe 364 032 2010-07-17 05:35 -a---
SKTools.exe 2 657 208 2010-03-02 15:09 -a---
ThemeChanger.exe 113 912 2007-04-18 07:43 -a---
Weather-iGo-PPC-v2.exe 264 192 2010-11-11 17:49 -a---
And only a few Exe seems to be work like my old test with my P535 long time ago...
it appear too somes EXE manage in .NEt/win32 are not supported actually !
But when it work... it s soooooooooooooooooo fastest !
Working file compression :
Code:
Explorer.exe 252 928 2010-09-07 20:46 -a---
GoogleMaps.exe 855 040 2010-06-25 19:47 -a---
iManager.exe 203 264 2011-02-21 17:00 -a---
Opera10-armv4i.exe 246 568 2010-03-15 20:48 -a---
PhotoManPro.exe 499 712 2010-04-26 16:29 -a---
RCapture.exe 53 248 2010-04-26 16:28 -a---
then i have seen on Mirolg ROM thread you manage a complete suite with standard TG exe... can you share this package, i think system files (*.exe) is universal...
And maybe you win when i will finish my new SKIN in test !
other nice idea to still use this tool always updated... i forgot it ! but it s very usefull !
Click to expand...
Click to collapse
I know .NET files cannot be UPXed, i did say this in my other post about UPX, but this thread was to state what i found could be done on mirom8.
Also bear in mind small files less than maybe 100k are not worth doing, because there is a latency involved with getting file off of storage, and then decompressing it in ram.
Also there is a downside, files UPXed have a higher memory footprint than files not compressed, so for instance, Imanager.exe that would always be resident in ram, is a bad idea, it will use more ram than it would if it wasn't compressed, its more useful for the config program, as that would make it open faster, any program that starts with the phone, don't bother UPXing it, any program thats always running, don't UPX it.
Glad you found the post useful.
then i will try to tes Mirom8 Rom and extract desired system files compresses based on your discussion with Mirolg...
thx for all !
lesscro said:
then i will try to tes Mirom8 Rom and extract desired system files compresses based on your discussion with Mirolg...
thx for all !
Click to expand...
Click to collapse
Mirom8 cfc is a beta and is not protected, so you can either ask Miro for what can and can't be done, or dump it in a kitchen and use it as a guide as to what to UPX and with what settings, not everything can be -Brute compessed, especially dll files, i believe there is a -Best switch, you will have to do a lot of trial and error, Miro has made leaps and bounds in finding what can be done, if you find things he has missed, let him know, anything to get a smaller, faster rom. My favourite example is the camera application, it fles, it opens in about 3 seconds.
Adding to your list of what you found could be done, i can tell you both of the largest files in the Opera application can be UPXed, so thats the exe and the largest dll file, in flashlite the largest dll can also be UPXed.
i will tru one by one Windows Exe files...
but i repeat i m pretty sure system base system is same on all rom especially system configuration files...
and All TG tool file, like camera and more other indispensable application...
You know what i m looking for... that's why i ask you to send me a package with already identified files system 'UPX transformed'...
I will won lot of time...
indeed, i will report your technic 'UPX' to a French Rom Cooker...
Actually my ROM, maybe it will try it himself too... and more tester more report !
have fun !
lesscro said:
i will tru one by one Windows Exe files...
but i repeat i m pretty sure system base system is same on all rom especially system configuration files...
and All TG tool file, like camera and more other indispensable application...
You know what i m looking for... that's why i ask you to send me a package with already identified files system 'UPX transformed'...
I will won lot of time...
indeed, i will report your technic 'UPX' to a French Rom Cooker...
Actually my ROM, maybe it will try it himself too... and more tester more report !
have fun !
Click to expand...
Click to collapse
Some components cannot be UPXed, cprog.exe, unless you first compress the png files, and gwes.exe, will eat more memory than ever if upxed, however if you found a technique to make it work postively on memory usage, please share how you did it.
I read some of this thread, maybe useful to you.
Only files i have are the ones listed in the first post, better off looking at miros roms as he has a lot of files upxed there.
Damn ! Beautifull... all your idea is awesome !
All your link is so cool...
i will try to test some new files... another tester is in place now... we will report all files we can test here !
Thx...
I can't seem to get the boot.img file to unpack, regardless of what tool I use or what os. I typically get the results below. the long term goal is to edit the boot.img to allow the next7p to use ext3 /system as opposed to cramfs, and give full read/write. It has been done by Wendal Chen on a different but similar tablet. (Both are rk29xx tablets.)
Any help would be appreciated.
I have been able to create a "custom" rom, which has root and SU, but you cannot write to the /system.
the boot.img from my custom rom is 598k The boot.img pulled from the tablet
is 4096K i get the same issues from both.
Code:
Welcome to the ZTE Racer kitchen by TigTex!
If you aren't using Windows XP, you might need to run this as admin
Make sure you have boot.img on the same folder as this file
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER: 1
Android Magic not found in boot.img. Giving up.
******kernel and ramdisk extracted!******
* Kernel is the "boot.img-kernel" file *
* Ramdisk is on gzip + cpio *
* YOU CAN ONLY EDIT RAMDISK ON LINUX *
* original img backed up as oldboot.img *
*****************************************
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER:
Ok so let's try the android kitchen
Here is the show boot.img information
Code:
Working folder's boot.img information
-------------------------------------
Kernel Size : 559903 bytes
Kernel Base Address : 0x00000000
Ramdisk Size : 2090599168 bytes
Ramdisk Load Address : 0x65545c0b
Second Stage Size : 779876570 bytes
Second Stage Load Address : 0xe1906573
Page Size : 84348953 bytes
ASCIIZ Product Name : (None)
Command Line: (None)
Press Enter to continue
And now the attempt to extract first using w option...
Code:
Working folder found
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Making folder BOOT-EXTRACTED ...
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Press Enter to continue
Ok so lets try the other option in the menu.
Code:
Press Enter to continue
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Contents of bootimg_010612_234100:
total 0
-rw-r--r-- 1 0 2012-01-06 23:41 zImage
Press Enter to continue
The zImage file it writes is 0k in size.
Here is the first line from the boot.img looking at it in the hexeditor.
Code:
00000000 4b 52 4e 4c 3a 93 08 00 1f 8b 08 00 00 00 00 00 KRNL:"...<......
From what I have read the kernel is supposedly starting at 1f 8b.....
getting the error that the Ramdisk is not there, it is almost like it is not a complete boot.img file. More so if I look at boot.img in a hexeditor and lookup that address. (Sigh) I keep plugging away.
any help is appreciated.
Dochoppy said:
I can't seem to get the boot.img file to unpack, regardless of what tool I use or what os. I typically get the results below. the long term goal is to edit the boot.img to allow the next7p to use ext3 /system as opposed to cramfs, and give full read/write. It has been done by Wendal Chen on a different but similar tablet. (Both are rk29xx tablets.)
Any help would be appreciated.
I have been able to create a "custom" rom, which has root and SU, but you cannot write to the /system.
the boot.img from my custom rom is 598k The boot.img pulled from the tablet
is 4096K i get the same issues from both.
Code:
Welcome to the ZTE Racer kitchen by TigTex!
If you aren't using Windows XP, you might need to run this as admin
Make sure you have boot.img on the same folder as this file
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER: 1
Android Magic not found in boot.img. Giving up.
******kernel and ramdisk extracted!******
* Kernel is the "boot.img-kernel" file *
* Ramdisk is on gzip + cpio *
* YOU CAN ONLY EDIT RAMDISK ON LINUX *
* original img backed up as oldboot.img *
*****************************************
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER:
Ok so let's try the android kitchen
Here is the show boot.img information
Code:
Working folder's boot.img information
-------------------------------------
Kernel Size : 559903 bytes
Kernel Base Address : 0x00000000
Ramdisk Size : 2090599168 bytes
Ramdisk Load Address : 0x65545c0b
Second Stage Size : 779876570 bytes
Second Stage Load Address : 0xe1906573
Page Size : 84348953 bytes
ASCIIZ Product Name : (None)
Command Line: (None)
Press Enter to continue
And now the attempt to extract first using w option...
Code:
Working folder found
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Making folder BOOT-EXTRACTED ...
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Press Enter to continue
Ok so lets try the other option in the menu.
Code:
Press Enter to continue
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Contents of bootimg_010612_234100:
total 0
-rw-r--r-- 1 0 2012-01-06 23:41 zImage
Press Enter to continue
The zImage file it writes is 0k in size.
Here is the first line from the boot.img looking at it in the hexeditor.
Code:
00000000 4b 52 4e 4c 3a 93 08 00 1f 8b 08 00 00 00 00 00 KRNL:"...<......
From what I have read the kernel is supposedly starting at 1f 8b.....
getting the error that the Ramdisk is not there, it is almost like it is not a complete boot.img file. More so if I look at boot.img in a hexeditor and lookup that address. (Sigh) I keep plugging away.
any help is appreciated.
Click to expand...
Click to collapse
Dsixda's kitchen has this feature, (un/re-pack) boot.img built in. Makes for very easy editing. Also helps for making your ROM.
Sent from my PC36100 using xda premium
jamieg71 said:
Dsixda's kitchen has this feature, (un/re-pack) boot.img built in. Makes for very easy editing. Also helps for making your ROM.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
That's what he said he used, but the kitchen does not support boot.img of his device's format. A lot of the cheaper tablets use a special format but I have seen Wiki guides on how they are built and extracted.
Any chance you know a link to one of the guides? I will also start searching on like tablets.
Dochoppy said:
Any chance you know a link to one of the guides? I will also start searching on like tablets.
Click to expand...
Click to collapse
Google for the "cmp738a" by Craig. It's a really ****ty tablet that I owned for one day. It uses cramfs like yours, and there are some links on how to unpack and create a ROM. Use terms like "cmp738a unpack ROM"
Dsixda: First thanks for your kitchen tool really it is a great piece of work, I am sure you are under appreciated for it.
After you told me to do some searches I did, then I looked back over everything I had been reading.
I can say I feel like an idiot. I was letting the big picture blot out the details so to speak.
Almost literally all I had to do was remove 3-4 bytes from the header, and ungzip the file...cpio etc etc.
I was stuck in the train of thought that I had to "unpack the boot.img" file first, then ungzip it...
Dochoppy said:
Dsixda: First thanks for your kitchen tool really it is a great piece of work, I am sure you are under appreciated for it.
After you told me to do some searches I did, then I looked back over everything I had been reading.
I can say I feel like an idiot. I was letting the big picture blot out the details so to speak.
Almost literally all I had to do was remove 3-4 bytes from the header, and ungzip the file...cpio etc etc.
I was stuck in the train of thought that I had to "unpack the boot.img" file first, then ungzip it...
Click to expand...
Click to collapse
You mean it's like any other boot.img except for the extra bytes at the beginning and a different header (instead of "ANDROID!" - the actual header the kitchen looks for)?
Well yes and no. The kitchen still does not extract the boot.img correctly, zImage is created as a 0k file, and the ramdisk is still not extracted.
Ok I am still missing something here.
Ok I am still missing something here.
dsixda-
Could you take a look at the boot.img file and tell me what I may be missing?
http://www.mediafire.com/?n9an9o5vmjida1c
I would appreciate it very much.
Dochoppy said:
Ok I am still missing something here.
dsixda-
Could you take a look at the boot.img file and tell me what I may be missing?
http://www.mediafire.com/?n9an9o5vmjida1c
I would appreciate it very much.
Click to expand...
Click to collapse
It's not going to work in the kitchen, what are you trying to do? It is missing the "ANDROID!" magic header and the rest of the file is in a garbled format. You'll need to Google for the solution for your device. I can't offer much help, sorry.
I understand that much. When you do a file boot.img command in linux it just comes back as DATA.
I'm not so much concerned with being able to use the kitchen on it as just being able to unpack and pack the file correctly, and completely.
Thanks for taking a peak at it.
Can you upload to dropbox and let me know. I was working on an experimental tool to do this, so an unknown device would be good to check.. I might be some time in getting back to you though
Sent from my HTC Desire using Tapatalk
Droidzone-
Drop box link
http://dl.dropbox.com/u/56600275/boot.img
Media fire link if that doesn't work.
http://www.mediafire.com/?n9an9o5vmjida1c
Thanks for taking a peak.
Could you also provide the full name of the tablet, manufacturer, and possibly a link to the device?
The tablet in question is the nextbook 7 premium
marketed in the US by E-fun. Website is www.nextbookusa.com
on the front of the page there is a link to the latest firmware which the current version of DocHoppy Rom is based on.
Thanks again for taking a peak at it.
I know this much, the boot.img file it's self once unpacked from the update.img file
is a gziped cpio file, with odd header and footer bits. I have been able to unpack the file (removing header info to make it gzip recognizable), and then using 7zip of all things to unpack the cpio portion. That is where I get hung up at. I need to unpack it correctly so it can be rebuilt correctly. By doing it the way I have, you can't rebuild the file properly.
Update:
After alot of research, and trial and error, I was able to correctly unpack and repack the boot.img. I flashed the repack to my tablet, and successfully booted.
Next step is to modify init.rc and convert /system to ext3.
I will keep you posted.
Do document what you did so that it helps someone else later
Sent from my HTC Desire using Tapatalk
I'm having a similar problem, posted about here. I don't understand why the Android magic number isn't making it into my kernel. I thought the kernel compile would be straightforward, but sheesh...
Dochoppy said:
Update:
After alot of research, and trial and error, I was able to correctly unpack and repack the boot.img. I flashed the repack to my tablet, and successfully booted.
Next step is to modify init.rc and convert /system to ext3.
I will keep you posted.
Click to expand...
Click to collapse
Hi, i am trying to extract a boot.img without the Android header too. What have you done to extract it?
Regards.
hi im newbie here this section about this tablet
yesterday i upgrade the tablet to version 4.0.x
My question is , how root it ?
Best Regwards
Nuno Rodrigues
Lisbon
Portugal
No root for ICS (OTA), yet...
ok ....
i will wait for that
thanks
See here: http://forum.xda-developers.com/showthread.php?t=1712150
It's an attempt on ICS root, and he needs testers. Since you have ICS, maybe you can give it a try. It's supposed to be harmless (please read that thread carefully), but I don't have ICS, so I can't really say...
Hi what is the zip i will install ???
Attached Files
File Type: zip 01 S update.zip - [Click for QR Code] (1.51 MB, 46 views)
File Type: zip 02 U update.zip - [Click for QR Code] (1.51 MB, 31 views)
File Type: zip 03 BB-SU.zip - [Click for QR Code] (1.14 MB, 39 views)
File Type: zip 04 Unroot.zip - [Click for QR Code] (241.4 KB, 28 views)
Click to expand...
Click to collapse
for root i think
No luck with the proposed files
I just tried to apply both updates (01 and 02) and both failed with "signature verification failed", tried to reply on the thread in development but I dont have enough points to do that.
Someone suggested to offer money to the developers to root the device, there is any place where I can send that money?
Thanks
I just tried to apply both updates (01 and 02) and both failed with "signature verification failed", tried to reply on the thread
Click to expand...
Click to collapse
I will wait for root
Thanks for all
Well, maybe next time it will work. What matters is that there's someone who's trying to root ICS. Let's hope success comes soon...
Hi all. Let's get right into this. I've searched through and not found anything relating to this model where de-brick or original ROM files are concerned. I did a lot of saerching online and found a file online -> HUAWEI_Y301-A1_V100R001C85B132_MPCS.rar <- which I've also uploaded to a Google drive. Still can't post links yet so change the link info so that you can get to the file.
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCNGJMMkxScVZyLVU/view?usp=sharing
I had a power cut when this was being uploaded - I think it finished but here are the hashes just in case:
Size: 440800365 bytes
ADLER32: dd052c58
CRC32: 314ea95f
MD2: f715fbc043377f30f0c6f92c1383f873
MD4: cdf28659286b47bf28f0bfb6210fe0c9
MD5: 6e4630c80f13235f12b07fa5bd5e7346
SHA1: afd4f30c15ba10c3327fa4455390018f96ae5837
SHA256: 2574ab1738009dac9898e08b57ad1ca03ed3e1c81144a72878f995b1eac72e81
SHA384: 38957eed51fcd2454cc2a0d94c4444f328aecdbc137f08573d089efd4e53ce0d486c475444b24ef4fbf9a391ec469b86
SHA512: 0a90b915141e63acef101e16dc83ac1e6659f44a153f16d72c5e7c18d87ef7be1331ba9475a14940fccd5fe40d9aeb13ac8f38a26890759fee16b3da56065d8d
RIPEMD128: f45c58b04184e4e122c5d4d8012ec53d
RIPEMD160: 1ba1ad8a75d1fb8e1344d8a42202bc2def7605ac
TIGER128: 5c53dfde6780cac34be867d862b913b3
TIGER160: 5c53dfde6780cac34be867d862b913b319cda8df
TIGER192: 5c53dfde6780cac34be867d862b913b319cda8df8b6dc1ba
GOST: 78b80fd7833de57d4ded26b64a7ca0586e9601e7cd7243e448cd997653957adf
Some persons may also want the drivers for this to be recognized when plugged in. That's in the next link:
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCMlBFQlNuYXZCeG8/view?usp=sharing
Hashes:
SIZE: 6698970 bytes
ADLER32: 769c16b0
CRC32: f0782916
MD2: a535a3cec1f0a612db9a580fd8b8fca9
MD4: 13580fd5702c7db7e0db223de67be8b4
MD5: f2d0ca441f5d28eb489e466afff7ead7
SHA1: 4af3bd670ffbe1b59bd193fd3ab03e5a2fc4d179
SHA256: b53efde84db8a8c93afcea30d0159e75af49ebf6352b7b34691fc4a142291eb1
SHA384: eaac94fcae45435bdbd44d98b6b001cc7b59adcf9f84c980cb3edba6d42eb8784323720df28a6076d59582788ff12af5
SHA512: bceef8964c38bcff785be78eb16aaa25de7c7510da8f63b31e118d5dc071c912399b40f5f5d9fccf6cd4dcd61b1d7543eb9175133aeff9404917a033f1aea3bf
RIPEMD128: 325cb61d9610cedd3aed33b2afd45a1d
RIPEMD160: ed2e20baaa9deb38ef4a792ddba127d23cf9ecab
TIGER128: 41646e0d7e97637ac837bfdc780513f6
TIGER160: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee
TIGER192: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee29d2db73
GOST: 23050f83375d15b1a22346c3ac7ddaa3d927ba97c81ba7b03d9f580a33b781e4
To continue here's the issue I'm having which I guess a few other persons have as well - the phone appears to be bricked. It powers on and either goes directly to a blue screen or shows the Huawei logo then goes to the blue screen.
After much searching I found the file I linked to. When extracted the file is 800+MB and gives you a file called UPDATE.APP when extracted and is in a folder called DLOAD which you're instructed to put in the root of your SD card and put in the phone.
My problem is this: It boots and seems to start a loading process but the bar sticks at about 30% and doesn't move. This may be because the memory in the phone is corrupted/bad but it could be that the file I'm using is wrong. Who knows? Anyways - this thread is started as both a question and an answer thread.
My questions would be - is there anything else to try?
The answers provided include the location of drivers, a firmware file and instructions on how to get it done.
I'd also like to add this document I found:
hxxps: //www .scribd .c0m/doc /215227240/Confidential-Huawei-y301-A2-v100r001c85b132-Upgrade-Guideline
This shows the process for the A2 but I believe it's applicable here.
Also I'd like to point out that I've found some other files online but the RAR file I mentioned is the only one with an UPDATE.APP file - others have actual files in there and I'm not sure if the UPDATE.APP is really just a ZIP file with the info or if it was created with some specialized program to have a certain structure or something.........not a dev so I don't know.
Additional info would probably be that I can get the phone to a pink/purple (I'm a guy - I'm color blind) screen by holding VOL+/VOL-/PWR but I'm unable to use any commands to find the phone - ADB or FASTBOOT - because the drivers I have only show the device as a COM port and a modem in Windows. Haven't tried in Linux.
Any assistance in this would be greatly appreciated. Thanks in advance.
When I get to my 10 posts or more then I'll post pics.
*EDIT*
I checked the SD card after the last update failure and found a file called SD_UPDATE.LOG. Contents are below:
filename = /mmc1/dload/update.app
call RCV_MODULE_END_EVENT failed,module = OEMSBL_VER_LIST
CMD=0xf,moduleaddr = 0xd2000000, len_tmp=0x4000
filename = /mmc1/dload/update.app
call RCV_MODULE_END_EVENT failed,module = OEMSBL_VER_LIST
CMD=0xf,moduleaddr = 0xd2000000, len_tmp=0x4000
Click to expand...
Click to collapse
*BUMP*
Nothing from nobody? No thoughts or suggestions?
IMO it seems like either there's something wrong with the internal memory or maybe the file I'm using is wrong?
khat17 said:
Hi all. Let's get right into this. I've searched through and not found anything relating to this model where de-brick or original ROM files are concerned. I did a lot of saerching online and found a file online -> HUAWEI_Y301-A1_V100R001C85B132_MPCS.rar <- which I've also uploaded to a Google drive. Still can't post links yet so change the link info so that you can get to the file.
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCNGJMMkxScVZyLVU/view?usp=sharing
I had a power cut when this was being uploaded - I think it finished but here are the hashes just in case:
Size: 440800365 bytes
ADLER32: dd052c58
CRC32: 314ea95f
MD2: f715fbc043377f30f0c6f92c1383f873
MD4: cdf28659286b47bf28f0bfb6210fe0c9
MD5: 6e4630c80f13235f12b07fa5bd5e7346
SHA1: afd4f30c15ba10c3327fa4455390018f96ae5837
SHA256: 2574ab1738009dac9898e08b57ad1ca03ed3e1c81144a72878f995b1eac72e81
SHA384: 38957eed51fcd2454cc2a0d94c4444f328aecdbc137f08573d089efd4e53ce0d486c475444b24ef4fbf9a391ec469b86
SHA512: 0a90b915141e63acef101e16dc83ac1e6659f44a153f16d72c5e7c18d87ef7be1331ba9475a14940fccd5fe40d9aeb13ac8f38a26890759fee16b3da56065d8d
RIPEMD128: f45c58b04184e4e122c5d4d8012ec53d
RIPEMD160: 1ba1ad8a75d1fb8e1344d8a42202bc2def7605ac
TIGER128: 5c53dfde6780cac34be867d862b913b3
TIGER160: 5c53dfde6780cac34be867d862b913b319cda8df
TIGER192: 5c53dfde6780cac34be867d862b913b319cda8df8b6dc1ba
GOST: 78b80fd7833de57d4ded26b64a7ca0586e9601e7cd7243e448cd997653957adf
Some persons may also want the drivers for this to be recognized when plugged in. That's in the next link:
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCMlBFQlNuYXZCeG8/view?usp=sharing
Hashes:
SIZE: 6698970 bytes
ADLER32: 769c16b0
CRC32: f0782916
MD2: a535a3cec1f0a612db9a580fd8b8fca9
MD4: 13580fd5702c7db7e0db223de67be8b4
MD5: f2d0ca441f5d28eb489e466afff7ead7
SHA1: 4af3bd670ffbe1b59bd193fd3ab03e5a2fc4d179
SHA256: b53efde84db8a8c93afcea30d0159e75af49ebf6352b7b34691fc4a142291eb1
SHA384: eaac94fcae45435bdbd44d98b6b001cc7b59adcf9f84c980cb3edba6d42eb8784323720df28a6076d59582788ff12af5
SHA512: bceef8964c38bcff785be78eb16aaa25de7c7510da8f63b31e118d5dc071c912399b40f5f5d9fccf6cd4dcd61b1d7543eb9175133aeff9404917a033f1aea3bf
RIPEMD128: 325cb61d9610cedd3aed33b2afd45a1d
RIPEMD160: ed2e20baaa9deb38ef4a792ddba127d23cf9ecab
TIGER128: 41646e0d7e97637ac837bfdc780513f6
TIGER160: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee
TIGER192: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee29d2db73
GOST: 23050f83375d15b1a22346c3ac7ddaa3d927ba97c81ba7b03d9f580a33b781e4
To continue here's the issue I'm having which I guess a few other persons have as well - the phone appears to be bricked. It powers on and either goes directly to a blue screen or shows the Huawei logo then goes to the blue screen.
After much searching I found the file I linked to. When extracted the file is 800+MB and gives you a file called UPDATE.APP when extracted and is in a folder called DLOAD which you're instructed to put in the root of your SD card and put in the phone.
My problem is this: It boots and seems to start a loading process but the bar sticks at about 30% and doesn't move. This may be because the memory in the phone is corrupted/bad but it could be that the file I'm using is wrong. Who knows? Anyways - this thread is started as both a question and an answer thread.
My questions would be - is there anything else to try?
The answers provided include the location of drivers, a firmware file and instructions on how to get it done.
I'd also like to add this document I found:
hxxps: //www .scribd .c0m/doc /215227240/Confidential-Huawei-y301-A2-v100r001c85b132-Upgrade-Guideline
This shows the process for the A2 but I believe it's applicable here.
Also I'd like to point out that I've found some other files online but the RAR file I mentioned is the only one with an UPDATE.APP file - others have actual files in there and I'm not sure if the UPDATE.APP is really just a ZIP file with the info or if it was created with some specialized program to have a certain structure or something.........not a dev so I don't know.
Additional info would probably be that I can get the phone to a pink/purple (I'm a guy - I'm color blind) screen by holding VOL+/VOL-/PWR but I'm unable to use any commands to find the phone - ADB or FASTBOOT - because the drivers I have only show the device as a COM port and a modem in Windows. Haven't tried in Linux.
Any assistance in this would be greatly appreciated. Thanks in advance.
When I get to my 10 posts or more then I'll post pics.
*EDIT*
I checked the SD card after the last update failure and found a file called SD_UPDATE.LOG. Contents are below:
Click to expand...
Click to collapse
khat17 said:
*BUMP*
Nothing from nobody? No thoughts or suggestions?
IMO it seems like either there's something wrong with the internal memory or maybe the file I'm using is wrong?
Click to expand...
Click to collapse
Sent from my SPH-L710 using XDA Premium 4 mobile app
Link error
Hi men i try to download the file from google drive but unfortunately the file star to download but dont finish, do you know if the link its updated
thanks for your help
regards
khat17 said:
Hi all. Let's get right into this. I've searched through and not found anything relating to this model where de-brick or original ROM files are concerned. I did a lot of saerching online and found a file online -> HUAWEI_Y301-A1_V100R001C85B132_MPCS.rar <- which I've also uploaded to a Google drive. Still can't post links yet so change the link info so that you can get to the file.
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCNGJMMkxScVZyLVU/view?usp=sharing
I had a power cut when this was being uploaded - I think it finished but here are the hashes just in case:
Size: 440800365 bytes
ADLER32: dd052c58
CRC32: 314ea95f
MD2: f715fbc043377f30f0c6f92c1383f873
MD4: cdf28659286b47bf28f0bfb6210fe0c9
MD5: 6e4630c80f13235f12b07fa5bd5e7346
SHA1: afd4f30c15ba10c3327fa4455390018f96ae5837
SHA256: 2574ab1738009dac9898e08b57ad1ca03ed3e1c81144a72878f995b1eac72e81
SHA384: 38957eed51fcd2454cc2a0d94c4444f328aecdbc137f08573d089efd4e53ce0d486c475444b24ef4fbf9a391ec469b86
SHA512: 0a90b915141e63acef101e16dc83ac1e6659f44a153f16d72c5e7c18d87ef7be1331ba9475a14940fccd5fe40d9aeb13ac8f38a26890759fee16b3da56065d8d
RIPEMD128: f45c58b04184e4e122c5d4d8012ec53d
RIPEMD160: 1ba1ad8a75d1fb8e1344d8a42202bc2def7605ac
TIGER128: 5c53dfde6780cac34be867d862b913b3
TIGER160: 5c53dfde6780cac34be867d862b913b319cda8df
TIGER192: 5c53dfde6780cac34be867d862b913b319cda8df8b6dc1ba
GOST: 78b80fd7833de57d4ded26b64a7ca0586e9601e7cd7243e448cd997653957adf
Some persons may also want the drivers for this to be recognized when plugged in. That's in the next link:
hxxps: //drive .google .c0m/file/d /0BztJaB5ODkRCMlBFQlNuYXZCeG8/view?usp=sharing
Hashes:
SIZE: 6698970 bytes
ADLER32: 769c16b0
CRC32: f0782916
MD2: a535a3cec1f0a612db9a580fd8b8fca9
MD4: 13580fd5702c7db7e0db223de67be8b4
MD5: f2d0ca441f5d28eb489e466afff7ead7
SHA1: 4af3bd670ffbe1b59bd193fd3ab03e5a2fc4d179
SHA256: b53efde84db8a8c93afcea30d0159e75af49ebf6352b7b34691fc4a142291eb1
SHA384: eaac94fcae45435bdbd44d98b6b001cc7b59adcf9f84c980cb3edba6d42eb8784323720df28a6076d59582788ff12af5
SHA512: bceef8964c38bcff785be78eb16aaa25de7c7510da8f63b31e118d5dc071c912399b40f5f5d9fccf6cd4dcd61b1d7543eb9175133aeff9404917a033f1aea3bf
RIPEMD128: 325cb61d9610cedd3aed33b2afd45a1d
RIPEMD160: ed2e20baaa9deb38ef4a792ddba127d23cf9ecab
TIGER128: 41646e0d7e97637ac837bfdc780513f6
TIGER160: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee
TIGER192: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee29d2db73
GOST: 23050f83375d15b1a22346c3ac7ddaa3d927ba97c81ba7b03d9f580a33b781e4
To continue here's the issue I'm having which I guess a few other persons have as well - the phone appears to be bricked. It powers on and either goes directly to a blue screen or shows the Huawei logo then goes to the blue screen.
After much searching I found the file I linked to. When extracted the file is 800+MB and gives you a file called UPDATE.APP when extracted and is in a folder called DLOAD which you're instructed to put in the root of your SD card and put in the phone.
My problem is this: It boots and seems to start a loading process but the bar sticks at about 30% and doesn't move. This may be because the memory in the phone is corrupted/bad but it could be that the file I'm using is wrong. Who knows? Anyways - this thread is started as both a question and an answer thread.
My questions would be - is there anything else to try?
The answers provided include the location of drivers, a firmware file and instructions on how to get it done.
I'd also like to add this document I found:
hxxps: //www .scribd .c0m/doc /215227240/Confidential-Huawei-y301-A2-v100r001c85b132-Upgrade-Guideline
This shows the process for the A2 but I believe it's applicable here.
Also I'd like to point out that I've found some other files online but the RAR file I mentioned is the only one with an UPDATE.APP file - others have actual files in there and I'm not sure if the UPDATE.APP is really just a ZIP file with the info or if it was created with some specialized program to have a certain structure or something.........not a dev so I don't know.
Additional info would probably be that I can get the phone to a pink/purple (I'm a guy - I'm color blind) screen by holding VOL+/VOL-/PWR but I'm unable to use any commands to find the phone - ADB or FASTBOOT - because the drivers I have only show the device as a COM port and a modem in Windows. Haven't tried in Linux.
Any assistance in this would be greatly appreciated. Thanks in advance.
When I get to my 10 posts or more then I'll post pics.
*EDIT*
I checked the SD card after the last update failure and found a file called SD_UPDATE.LOG. Contents are below:
Click to expand...
Click to collapse
Uploading to another source as I post this. I think I have enough posts now to put an actual link.
*EDIT*
FILE: https://mega.nz/#!gQcS3ATQ!MRN_P4yoYHA9xhB3crKjCtfXZ314xmpF5Z_E2rmPLEM
DRIVER: https://mega.nz/#!sVF2GQDA!17Yoz8LzF5_hipCY0OI83wR8yP8Qcy2ONqvTD56hx5Q
The hashes remain the same.
FILE HASH
Size: 440800365 bytes
ADLER32: dd052c58
CRC32: 314ea95f
MD2: f715fbc043377f30f0c6f92c1383f873
MD4: cdf28659286b47bf28f0bfb6210fe0c9
MD5: 6e4630c80f13235f12b07fa5bd5e7346
SHA1: afd4f30c15ba10c3327fa4455390018f96ae5837
SHA256: 2574ab1738009dac9898e08b57ad1ca03ed3e1c81144a72878 f995b1eac72e81
SHA384: 38957eed51fcd2454cc2a0d94c4444f328aecdbc137f08573d 089efd4e53ce0d486c475444b24ef4fbf9a391ec469b86
SHA512: 0a90b915141e63acef101e16dc83ac1e6659f44a153f16d72c 5e7c18d87ef7be1331ba9475a14940fccd5fe40d9aeb13ac8f 38a26890759fee16b3da56065d8d
RIPEMD128: f45c58b04184e4e122c5d4d8012ec53d
RIPEMD160: 1ba1ad8a75d1fb8e1344d8a42202bc2def7605ac
TIGER128: 5c53dfde6780cac34be867d862b913b3
TIGER160: 5c53dfde6780cac34be867d862b913b319cda8df
TIGER192: 5c53dfde6780cac34be867d862b913b319cda8df8b6dc1ba
GOST: 78b80fd7833de57d4ded26b64a7ca0586e9601e7cd7243e448 cd997653957adf
DRIVER HASH
SIZE: 6698970 bytes
ADLER32: 769c16b0
CRC32: f0782916
MD2: a535a3cec1f0a612db9a580fd8b8fca9
MD4: 13580fd5702c7db7e0db223de67be8b4
MD5: f2d0ca441f5d28eb489e466afff7ead7
SHA1: 4af3bd670ffbe1b59bd193fd3ab03e5a2fc4d179
SHA256: b53efde84db8a8c93afcea30d0159e75af49ebf6352b7b3469 1fc4a142291eb1
SHA384: eaac94fcae45435bdbd44d98b6b001cc7b59adcf9f84c980cb 3edba6d42eb8784323720df28a6076d59582788ff12af5
SHA512: bceef8964c38bcff785be78eb16aaa25de7c7510da8f63b31e 118d5dc071c912399b40f5f5d9fccf6cd4dcd61b1d7543eb91 75133aeff9404917a033f1aea3bf
RIPEMD128: 325cb61d9610cedd3aed33b2afd45a1d
RIPEMD160: ed2e20baaa9deb38ef4a792ddba127d23cf9ecab
TIGER128: 41646e0d7e97637ac837bfdc780513f6
TIGER160: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee
TIGER192: 41646e0d7e97637ac837bfdc780513f6aaa6b2ee29d2db73
GOST: 23050f83375d15b1a22346c3ac7ddaa3d927ba97c81ba7b03d 9f580a33b781e4