This thread is now retired, a direct convert CC to OEM is done successful so please check that:
http://forum.xda-developers.com/ascend-mate2/general/guide-cc-variant-to-oem-convertion-t3149767
****** Following is orig thread ********
Now official release is out, and I'd like to start this thread to show my plan and the progress.
So far, we did not see anyone have CC can update to L. And also a official B148 full flash image is there, addition to B309 image. so, if anyone done that on CC, then this task is useless, so pls let me know if that happened.
My plan is to develop the twrp script to repartition system to 1.8gb, I found some doc already, will post below, then after testing that works fine, I will publish here.
See this post for more info
http://forum.xda-developers.com/showpost.php?p=61585912&postcount=398
But it is still in early stage, and I have daily job and off school kids, and need put phone back to working state everytime, so the progress maybe slow.
Also, any suggestions or questions are welcome.
reserved
This is the link
http://forum.xda-developers.com/xia...rtition-capacity-t3011918/page19#post59863033
Warning, repartition is very dangrous in nature, so if want to do it yourself, you should know what you are doing.
Right now, to minimize the risk, we only need re-orgnize the last 3 partitions. The boot and recovery partition is increased to 64M, but the old size is good enough. I already tested the 12M boot image (cut from 5.1)can boot fine.
Looking forward to help with testing.
BTW, When trying to flash the TWRP backup we had of the beta, I did get a sizing error on the BOOT, independent of the SYSTEM sizing error.
Here is a pic.
All the best xordos, you're our saviour !!
ArkAngel06 said:
Looking forward to help with testing.
BTW, When trying to flash the TWRP backup we had of the beta, I did get a sizing error on the BOOT, independent of the SYSTEM sizing error.
Here is a pic.
Click to expand...
Click to collapse
That expected, as it is image, so 64MB wont fit in 12M partition. I checked the useful part is less than 12M, so after trim the image to 12M then flash, it still boot fine. But this is my init test, I didnot get chance to actual downgrade to 148, will reconfirm later
Thanks xordos for your efforts. We will look forward to updates but I do have one question that bothers me. Why do we have to modify partitions again when this was already done on previously converted CC devices to OEM version.
For people who have it converted to OEM from CC earlier. Shouldnt they be able to flash the lollipop update just like all other OEM folks?
So far I think it is a partial flash, system and a few other partition is flashed to B148, though about page show B148, but it is still CC. At least huawei dload updater refuse to upgrade those phones.
I think there is some where hidden huawei found out it is still CC. I dont have this phone, so I can't do much.
Xordos, you are very kind to help the CC users. I have already mashed your Thanks button.
Xordos, you're moving in wrong direction. It's better to find a way to convert CC to OEM completely.
Kostyan_nsk said:
Xordos, you're moving in wrong direction. It's better to find a way to convert CC to OEM completely.
Click to expand...
Click to collapse
The question is do you have an idea of what it takes to convert CC to OEM or are just thinking that'll be the better way to go ?
medwatt said:
The question is do you have an idea of what it takes to convert CC to OEM or are just thinking that'll be the better way to go ?
Click to expand...
Click to collapse
Yes, I have and I'm trying with ArkAngel06. But without success at this moment. Things would go better if xordos could provide me data from his device, but he ignored my PM...
Kostyan_nsk said:
Xordos, you're moving in wrong direction. It's better to find a way to convert CC to OEM completely.
Click to expand...
Click to collapse
I can see where xordos is coming from... The Nexus 6 has a few carriers and they have slightly different versions for all but what they have is 1 zip version for all the carriers.
The main problem we are having is this:
We are trying to flash basically all the partitions that changed from CC to OEM to try and have the update.app see the CC as OEM.
However, b148 doesn't have an update_vendor.app file, and yet I get this error when flashing.
Error
Proof that it's only update.app in dload folder.
I did a search on the whole phone for update_vendor.app and it shows nothing. Ii formatted my SDcard and made just the one dload folder and it still says the update_vendor.app error. There is also definitely nothing on my internal SDcard either.
Anyone have any ideas?
Kostyan_nsk said:
Yes, I have and I'm trying with ArkAngel06. But without success at this moment. Things would go better if xordos could provide me data from his device, but he ignored my PM...
Click to expand...
Click to collapse
Hehe, no I am not ignoring you, I didn't check PM until just saw your post, sorry.
Yes, i can share oem partition to you as long as it is not published. If we can convert CC to OEM, that will be perfect solution. I will upload after work. I am in us central time.
Again, as discussed last time, I am still not comfortable share that to public, call me super causious.
Huawei update.app extractor will show you why. The model number is embedded.
It is possible to make a universal flashable zip that will do it. Just as any CM rom does.
It will overwite your EFSl SO someone needs to make a flashable CC rom as well in case anyone wants to go back to stock.
ArkAngel06 said:
The main problem we are having is this:
We are trying to flash basically all the partitions that changed from CC to OEM to try and have the update.app see the CC as OEM.
However, b148 doesn't have an update_vendor.app file, and yet I get this error when flashing.
Error
Proof that it's only update.app in dload folder.
I did a search on the whole phone for update_vendor.app and it shows nothing. Ii formatted my SDcard and made just the one dload folder and it still says the update_vendor.app error. There is also definitely nothing on my internal SDcard either.
Anyone have any ideas?
Click to expand...
Click to collapse
Don't pay attention to update_vendor.app anymore.
There are two variants: recovery renames update.app to update_vendor.app or it's just fixed error message whatever update.app or update_vendor.app is.
---------- Post added at 22:50 ---------- Previous post was at 22:34 ----------
If anyone else has OEM device, still runs B148 and wants to help, then your help would be very appreciated.
Kostyan_nsk said:
Don't pay attention to update_vendor.app anymore.
There are two variants: recovery renames update.app to update_vendor.app or it's just fixed error message whatever update.app or update_vendor.app is.
---------- Post added at 22:50 ---------- Previous post was at 22:34 ----------
If anyone else has OEM device, still runs B148 and wants to help, then your help would be very appreciated.
Click to expand...
Click to collapse
Can we not extract whatever files or partitions needed from B148 image (rom) itself. I believe that has been publicly posted already. Is there anything specific that changes on the actual device after flashing. I would think all the files and device ID's can be extracted from the B148 image file that is available?
Shortly: no, it's not!
Related
Hey guys, there's a ton of confusion going on because of partition tables and what not. The Galaxy Player 4.0 uses a BML partition table. The Galaxy Player 5.0 uses a MMC block partition table. I ran into problems with 8g versus 16g partition tables because the 8gig won't work on the 16gig and vice versa. We need a master list of PIT files. This is that master list.
International is the standard version. Because of copyright problems, US versions may be different.
PARTITION TABLES
Galaxy player 4.0 16gig thanks some korean site.
Galaxy Player 4.0 US 8gig thanks hyperrunner
Galaxy Player 4.0 International 8gig thanks zaclimon
Galaxy Player 5.0 16gig thanks ishish9
Galaxy Player 5.0 US 8gig thanks redpirate8
Galaxy Player 5.0 International 8gig thanks aillez
Please post your partition table and I will link it in the above. If you have one which is not in the list, let me know.
How to obtain your partition table
Download Heimdall Suite here: http://www.glassechidna.com.au/products/heimdall/
Open "heimdall-frontend"
if you encounter errors in windows, you need to install the zadig libusb driver. Remember to "show all" from the menu in the program.
Put your device in Download mode
Click the Utilities tab
select an output filename. The file should always end with a "pit" I'd recommend something descriptive. eg..
GalaxyPlayer4.0-16G.pit, or G70-GalaxyPlayer5.0-8gig.pit
upload that file to http://mediafire.com
I recommend Mediafire because they have no distracting adds, no 50 second wait time, no signup, and everything is straight forward as opposed to 99% of the other file hosting sites.
post the mediafire link here in the forum
Ok, first, I don't think there are 16gb versions, other than maybe one for korea?
Second, The main issue here is the international version vs. the U.S. version, I believe there is quite a bit of difference in the firmwares of these versions, so you should probably have sections for "U.S. 4.0, U.S 5.0, International 4.0, International 5.0"
You might get more positive results that way
I am needing the 4.0 U.S Pit, btw, so thank you for creating this thread!
Edit: also, didn't you say in your other thread that heindmall doesn't work with these?
Here you go,
DOWNLOAD
P.S. - I couldnt get it the way you asked me so i ran terminal and used this code.
dd if=/dev/block/bml2 of=/sdcard/part.pit
Also this is the Samsung Galaxy Player 4.0 U.S. 8GB Version
Thanks, but it still doesn't work!? Stuck at "set partition" forever!
Wonder y hmmm..
Hyperrunner said:
Wonder y hmmm..
Click to expand...
Click to collapse
You need to get the Heimdall partition. I observed the same behavior before. and I was thinking it was a fluke.. It looks like on this device the heimdall dump will set the partitions, a bml dump wont.
I'll remove that and we're back at square one.
We could really use some participation here. You'll be thankful if you brick your device. Currently there are no recovery options... This is part of creating the first one ever.
Yeah i have been trying that but Heindall says that libusb error 13 for some reason i would get it but i cant since the error. Do you got a solution for it. I would do it but i cant get pass that error? I've tried installing libusb.
Hyperrunner said:
Yeah i have been trying that but Heindall says that libusb error 13 for some reason i would get it but i cant since the error. Do you got a solution for it. I would do it but i cant get pass that error? I've tried installing libusb.
Click to expand...
Click to collapse
Try making sure you have the samsung usb drivers installed; http://forum.xda-developers.com/showthread.php?t=961956
and usb debugging enabled in /settings/applications/development. After that is enabled, just plug it into the pc, don't select connect to computer.
All that is installed, just cant seem to connect ive checked everything.
You are going into download mode, correct?
Edit: Do you have the proper package for your os?
Adamoutler, have any advice?
Edit2: Figured it out, go to "drivers" in the heindmall file, run the zadig.exe, select "list all devices" in options, then install "Samsung composite USB".
Worked for me!
Edit 3 : Thanks i got it, i guess win was'nt detecting it.
Download
look at my previous post I edited.
iJimaniac said:
Try making sure you have the samsung usb drivers installed; http://forum.xda-developers.com/showthread.php?t=961956
and usb debugging enabled in /settings/applications/development. After that is enabled, just plug it into the pc, don't select connect to computer.
Click to expand...
Click to collapse
Don't listen to this. He does not know what he is talking about.
Make sure you select all in zadig, and try rebooting.
Yup all done and posted. Hope it work, please keep me updated on it.
Hyperrunner said:
Yup all done and posted. Hope it work, please keep me updated on it.
Click to expand...
Click to collapse
EDIT:
Nevermind it doesn't work. DO NOT FLASH THIS PIT FILE. Now I get a bunch of E: failed to mount errors.
Now I'm bricked too. Need a valid PIT file to flash back to stock.
WAIT, ive seen some videos in which you flash it. Most of them the md5 or tar file contains more stuff other than factoryfs.rfs and zImage.
Or is that ok since its not a phone if it is not or there is a problem just tell me and give me the commands to retrieve these needed files and i will make a new Firmware.
EDIT 2 Look im trying my best i can. I have never used odin or kernal and all the other files md5 or commands so dont give me any crap. Ive been trying to help you guys from the start. Im trying to learn while doing this it is not simple. Other morons would not even get passed the commands on terminal. If you dont want my help well then you wont get it. Currently im the only one helping you guys. As i said in the post above me if you need any other files in the md5 just give me the commands and i will reupload them.
EDIT 3 NVM
Ok, I think I know what to do, but we should move to a new thread in "general" so we don't clutter up this thread
You start it. You really need to reply faster.
iJimaniac said:
Ok, I think I know what to do, but we should move to a new thread in "general" so we don't clutter up this thread
Click to expand...
Click to collapse
Go ahead and clutter it. As long as we get a complete list, were fin
Hyperrunner said:
Edit 3 : Thanks i got it, i guess win was'nt detecting it.
Download
Click to expand...
Click to collapse
This is a USA 4.0 correct?
Hi! So I'm wondering if anyone know if there is\have been any development for
the Tizzbird Stick N1 (M\G) ?
We have this Android-stick in stock at my store, but I'm not sure if I'm going to get it or not yet. Depends the development, as I'd really like to see the capabilities for it. I believe it's a lowbrand tho. so I might be out of luck.
Anyone know anything?
I searched the forums, and did a google search. Didnt find much.
regards,
Dag M.
Hi there!
I own one of those, and there are a handful of (german-speaking) people activly posting in this forum http://forum.tizzbird-tv.de/ about the Tizzbird N1. - The problem with that forum is that they heavily censor it - as soon as anyone posts info on how to "get in", or if someone asks uncomfortable questions - those posts gets deleted.
They sell it really cheap for 30€ (not all the time, but twice for one day @ redcoon) and although the Wifi-Chip (or the drivers for it) are really crappy, the media player part is really nice.
update: I've did a little research, and here is a little list of relevant links about the tizzbird n1:
==== Marketing Product Pages ====
http://valueplus.co.kr/english/product/product_player_n1.html
http://www.tizzbird.com/eng/index.php?mm_code=719&sm_code=755
http://tizzbird-tv.de/tizzbird/tizzbird-n1.html
==== Official Firmware ====
http://www.tizzbird.com/eng/index.php?mm_code=726&sm_code=727&board_search_head_word=stick+n1
http://download.tizzbird-tv.de/TizzBird_N1G_update_GMS_V3_20_13072719.tzbird
==== German Support Forum (posting info about root-access prohibited) ====
http://forum.tizzbird-tv.de/viewforum.php?f=11
==== GPL-Code for Tizzbird N10, N20 & N30 - but not for N1? ====
http://www.tizzbird.com/eng/index.php?mm_code=752&sm_code=754
==== Kernel Sources ? ====
http://www.cnx-software.com/2012/03...k-n1-android-ics-hdmiusb-dongle-media-player/
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
https://github.com/cnxsoft/telechips-linux
Yeah, the pretend to be "community friendly and supportive" but once you actually start digging in, they get quite agressive and boot you out.
Anyways, I got a N1 a couple of days myself now (snagged it for 30 bucks at another RedCoon sale ) and I am surprised.
Got it pretty much only to tinker around with it and this thing suits more perfectly for that than I imagined.
Esp. that fact they used a simple SD card as "internal flash storage" - my guess is because a simple SD is cheaper than an actual eMMC flash chip, but it's so cool on so many levels for us.
I already found out how to replace the 4GB SD with a bigger one (have a 16GB in mine ATM).
I'll post some more details about it here later, got a few things I want to test and/or prepare first (thinking of some "easy to use cloning script"), but long story short:
You need to copy the bootloader to the very end (last few blocks) of the SD you want to use.
Once the BL is at the proper place it already boots from the new SD again, to be sure everything is as it's supposed to be one should apply an update via USB (I'm not 100% sure about a possible pointer to the BL that needs to be corrected, which the update does).
After that the partition information has to be edited to make the userdata partition larger and you're done.
thanks for the info HellcatDroid!
It would be great if you could elaborate on how to put the bootloader at the end of the sd-card.
Also I would love to get info how to get root into the stock firmware, that crippled down root-firmware that they allow to exist in the official tizzbird forum doesn't really satisfy my needs
I did it via a hex editor, but it should be doable with a few "dd" commands as well - that's one of the things I still want to try, find the propper dd params to copy the BL over.
If you dumped the original SD into a file using dd, at the very end of the image file you will find the bootloader and the very last block of the SD is a "header" telling the bootrom of the N1 a few things about it, so it can properly locate and load it.
So what you got to do is to copy those last ~230k from the image to the end of the new SD card.
As said, I'll try to write a small shell script that does it.
The rooting is even more easy (Stonecold would kill me if he'd read this, lol):
For when running on Linux (no can do on Windows, as Windows doesn't know the ext4 FS):
Since you got the SD in your PC anyways already, just mount partition 2 (e.g. if the SD is sdc on your PC, mount /dev/sdc2).
That is the partition where the Android system is sitting on.
Then just copy over the files needed for root to where they need to go, chown/chmod them properly, unmount and done
I used the "update-supersu.zip" I had for my Nexus7 to grab the required files.
But I'm planning to make a simple rooting script as well.
So if all goes as planned it'll come down to
- insert original SD
- run script 1
- insert new SD
- run script 2
- to root run script 3
brilliant! I would love to see those scripts
way easier than start tinkering with that stuff myself
One thing I wonder about - over at the official forum you said that a simple dd copy didn't work - is that if the target sd-card is bigger or also for an sd-card of equals size? because with equal size simple dd copy of the sd-card should still work, even if some things need so be exactly at the end.
Yup, just a dd didn't work because the new SD card was larger and the bootloader ended up being somewhere in the middle of the card instead of at the end.
While your thought of "dd to equal size cards" is totally correct, it might still fail due to the fact every card is not 100% exact same size counting down to last byte.
There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end.
If, however, the size of the cards is 100% the same, down to the last byte, then yes, a simple dd clone would work.
HellcatDroid said:
... There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end. ...
Click to expand...
Click to collapse
Oh! Didn't know that. I thought same marketing size means not the same size they write on the box, but at least the same size between those that are marketed with the same GB numbers on their stickers.
OK, here we go, I slapped together a few scripts for prepping a new (and larger) SD card to work in the N1 and while having the SD in the PC to aplly some root.
* hints at attachment of this post
The scripts might still have problems and not work on any Linux out there, but it's a start.
If there's more people interested and joining in on this I might continue but for now I got what I wanted - more storage and root.
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Could you post how you got there? what did you do to the sd-card that destroyed it?
Hi.
If you got a dump from a working state of the SD you can just dd it back onto the card.
If you don't, it can still be recovered but might need bit more work.
Two options:
find someone who gives you a dump of their card and use the write-card script from my above post to write it to your SD.
Problem with this: a working dump contains copyrighted code, like the bootloader, it technically it's "not OK" to share it
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu)
Option 2 would be nicer, IMO.
I'll try to make up said script
Thank you for your immediate answer!.
Actually I dont know what has happened, maybe the sharp instrument I used to remove the plastic cover scratch it...But now when I put it in a card reader the led of the reader switch off and the card is heated!!!. And also when I put it in the N1 the blue led turns off!.
So I bought a new empty micro Sd .
Waiting for your script to partition the new card and then boot in recovery mode and install a firmware....
Because I am not expert to linux please give me a lot of details how to do this.
Thanks again!
HellcatDroid said:
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu
Click to expand...
Click to collapse
Do you think the bootloader is even part of the offical updates? wouldn't it be "best practice" to leave the bootloader partition alone as long as possible (and normally firmware updates don't need to change the bootloader)
update: something else I've just found, those might be kernel sources for our Tizzbird N1:
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
-->
https://github.com/cnxsoft/telechips-linux
Yep, the bootloader is in the update - at least in the 3.20 one.
And yes, usually the bootloader shouldn't be touched because that's usually the one thing that can "perma-brick" Android devices.
However, sometimes the manufacturer updates it (fixing bugs, adding functionality) - on my Nexus7 they updated the bootloader on pretty much every update and also Samsung updates their bootloaders every now and then (and every single update flashes the current one).
Last, not least, on the N1 the bootloader isn't on a partition but at unpartitioned space at the very last blocks of the SD (=> reason for a simple dd to a larger card not booting).
Ohyay at the possible kernel sources!
It'd be so cool if that's really sources able to build a kernel for the N1 with - I think we might be able to even get custom recovery (CWM and the likes) on the N1 if those sources work
OK, while trying to recreate a working SD card w/o using a dump of a working one I found out a few more things - some of them still need figuring out if we wanna do it properly.
There seem to be TWO bootloaders!
A stage1 bootloader of ~1kB size located at the third and second last block of the SD. If it's missing the N1 can't boot and it looks like ARM code (haven't tried to disassamble it yet), I assume the bootrom loads and executes that piece of code which in turn parses the header (see below) and load/starts the stage2 bootloader (the one also found in the FW update).
The very last block of the SD is a "header block" with some information beeing parsed either by the bootrom or (more likely) the stage1 bootloader.
The headerblock contains (among numerous other unkown data) the size of the ("stage2") bootloader (the one that then actually loads and boots the Linux kernel of the Android OS, this is also the one contained in the FW update) and the usable size of the SD card! (everything works fine though if the SD size is wrong and a proper FW update updates the header during writing of the bootloader and also sets the correct size).
Also, the headerblock has a checksum of which I have no clue on how it is generated.
All that is just educated guesses and might be totally off, but for now it looks like it's not too far off.
So, for now we can assume the following boot sequence:
Boot-ROM
-> loads stage1 bootloader from fixed position "SDsize - 3 blocks" (1 block = 512bytes)
stage1 bootloader at fixed position on SD
-> checks checksum of headerblock (?), gets size of stage2 bootloader from headerblock, locates stage2 bootloader based on it's size and loads/executes it
stage2 bootloader on variable position on SD
-> base initialisation of hardware
-> checks for recovery trigger (the red button on the remote control) and boots kernel from partition 6 if trigger present
-> boots kernel from partition 1 if recovery was not triggered
-> enters fastboot mode when booting the kernel fails
Kernel
-> loads base drivers and boots up the system
you're brilliant Hellcat!
And did you also find both bootloader stages inside the firmware updates?
Another question that came to my mind while reading your post (fastboot..)
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
sebastian.heyn said:
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
Click to expand...
Click to collapse
Welcome to our rouge and non-censored Tizzbird N1 forum Sebastian!
I wonder if you found us here, if the German Tizzbird support also already knows about us
update: I just remembered, I've sent you the link as PM over in the official forums, thats how you landed here.
Sharing your sd-card image might be a copyright violation, and if you're profile name is strongly linked to you're real identity you should definitly be cautious with such things on public forums...
kaefert said:
And did you also find both bootloader stages inside the firmware updates?
Click to expand...
Click to collapse
Nope, unfortunately the stage1 bootloader is not in the update :-/
kaefert said:
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
Click to expand...
Click to collapse
Yeah, it works, even officially XD
Go to the TizzBird settings -> "System Settings" -> "Advanced Settings"
It has an option "OTG Mode" there, set it to "Debug".
If you have your N1 connected to your PC via the micro-USB port (and hence your PC powering the N1!) you can use ADB and fastboot just as usual
I have not yet tried if that option is persistant, i.e. it survives a power loss.
When booting the kernel fails it should fall back to fastboot mode, so flashing a new kernel w/o pulling the SD should be possible - need to test this a bit more, though.
What works is, if you're rooted and and you fire the command "reboot bootloader" from a root shell, that gets you into fastboot mode no matter what (given you applied above mentioned setting first).
But needing a running system to get into fastboot mode kinda defeats the purpose of it - this aint Ouya which is a total fail when it comes to fastboot XD
---------- Post added at 09:26 AM ---------- Previous post was at 09:05 AM ----------
kaefert said:
I wonder if you found us here, if the German Tizzbird support also already knows about us
Click to expand...
Click to collapse
Eventually they will, I'd say.
And I'd love to see their faces when they do XD
Ok so I'm what you guys would call a newbie with Android, I've been an iPhone user for years (switched from Verizon to AT&T to get the iPhone because at the time it was an AT&T exclusive). However I'm a really big Google enthusiasts so I have followed Android from inception. Growing tired of how bad AT&T's reception was in my house I recently switched back to Verizon and I purchased the GS4. I'm very happy that I can make calls without the use of a Micro Cell, truthfully reliable coverage was the biggest reason why I switched carriers. Else I would probably got the GS4 or HTC 1 on AT&T.
Being a newbie I made some noob mistakes, however I'm glad to report non of my mistakes bricked my phone. My phone works flawless it's only the stock recovery that is jacked up. So to start off I naively though all S4's were 100% open when rooted, by that I thought I could simply install any ROM I wanted to as long as I was rooted. However it appears that Verizon made Samsung lock the firmware with the OTA updates, from what I gather now after reading is the initial firmware was ok but the subsequent OTA downloads introduced the locked boot. Which sucks for me because I willingly took both updates which put the ME7 and now the MI1 builds on my device.
When I started to root process I had the MI1 build and I performed the De LaVega root method (thank you Tomsgt for your videos)! At the time of root and right after the root I was still not aware of the difference with builds. At that point I attempted to install TWRP via GooManager, since I had the MI1 build it did not work. GooManager kept telling me there was no file for my phone or something similar.
Now this should have been huge red flag for me but I was persistent and I looked on TWRP's website and found the file for my phone along with the manual install instructions. I'm familiar with using a Linux command line so followed the instructions to write TWRP into /dev/block/mmcblk0p21 on my device.
After reboot my device failed to get into stock recovery mode, instead it goes back into download mode but has an extra line of text that says "Could not do normal boot". Since I originally hosed my stock recovery I have read up on the different builds and I have also successfully installed the clockmod recovery option. That all works fine it's just factory recovery is still hosed up and it's annoying me!
I know that was a bit long winded but wanted to give a little background. Now I hope I'm not the only guy/girl who has jacked up the stock recovery section. I was hoping someone had some instructions to fix. Heck I think (but I'm not 100% sure) that if I can get someone who still has stock recovery to copy/export what they have in /dev/block/mmcblk0p21, then I can download that file put on my sd card and then write that back into my system using the same dd input/output command I did before.
May not be that easy but that's what I'm hoping for, or maybe some suggestions. :fingers-crossed:
Thx,
Joe
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
kennyglass123 said:
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Click to expand...
Click to collapse
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
garzjoe said:
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
Click to expand...
Click to collapse
Bump....
Still hoping there is someone out there who can help me out.
garzjoe said:
Bump....
Still hoping there is someone out there who can help me out.
Click to expand...
Click to collapse
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
southpaw5271 said:
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
Click to expand...
Click to collapse
Hmm I can investigate that but my phone is not bricked. I'm using it now to reply to you. Stock recovery is hosed...so when I power off and then hold Vol+, Power, Home key and then let go of power and keep holding the other two buttons. That key sequence gets my phone into recovery mode. However I can't get into that with my phone anymore.
Thx,
Joe
For now simply follow the instructions and use the provided file download from the link posted below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
I have personaly tested this method in full on My AT&T Samsung Galaxy S4 ZOOM SM-C105AUCUAMJ2 (4.2.2 Jelly Bean)
although it should be safe to use on any AT&T Samsung Galaxy S4 ZOOM running an android version prior to Kit-Kat
All Credit for this, "exellent completely safe", Root method goes to its creator k1mu
And please Know that it is only being shared with you via his explicit permission.
EDIT:
Q&A for [ROOT] Saferoot: Root for AT&T Galaxy S4 ZOOM SM-C105AUCUAMJ2_On 4.2.2 JB
Please if you are not on an AT&T Galaxy S4 ZOOM C-150a, Feel Free to Read
but Do not seek help,instruction, or any other type of advice by posting in this thread as it is hard enough to find information about a specific device when the said device does not have a dedicated forum. Thank You for your Understanding in this.
Instructions & Advice
If ?'s arise
and time allows I will add device specific instruction as well as any advice, Please bear with me. Same as above Q&A Link
Will this same method also work on the SM-C105AUCUAMJ2?
kbracing6 said:
Will this same method also work on the SM-C105AUCUAMJ2?
Click to expand...
Click to collapse
Most Definitely as this was the reason for my post
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
thisisapoorusernamechoice said:
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
Click to expand...
Click to collapse
Thanks My guy,
This definately gives me a good jumping off point.
The phone shipped with JB-4.2.2 and I think there has been an AT&T OTA for KK so it would have to be a complete Firmware so thats good news.
I'm working on several projects at once so I don't know exactly when I'll get to this but when I do the first thing will be to verify whether the .img's for data/system/cache are img.ext4 or not and if not how to produce correctly.
Also I don't have a Linux Dev setup yet I'm running Windows On a 2011 Dell XPS-17_L702x with an intel 2720 quad core. So from your post I take it Ubuntu would be your suggestion for Linux Distro. and should I make a separate Linux Partition and run from it, or run from a VM-Box inside of windows? Which do you think would be most efficient?
Now that I think of it I'm going to start a dedicated thread for development discussion for this specific device. If I start the thread in the Development section for the general S$-ZOOM but title it specifically for the " AT&T-C105a_ZOOM " do you think the mods would want to move it to the general Q&A section?
" I would hope that, as it would pertain directly to the development of the specific device they would see fit to leave it in the development section.
Sorry for the randomness of my thoughts but I will link you to the thread when I get around to starting on it.
For now I'm going to get back to work on the S4_Active for My daughters B-day I intend to have it Rooted and rommed out for her. When I get that done I'll make my way back to this Project, and start the dedicated thread.
Thanks again,
" I look forward to future collaboration as it seem we share a similar Hobie at the least ",
Phatboyj
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
capt_planit said:
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
Click to expand...
Click to collapse
What is your build # because this is a fully effective root method for the ATT SM-C105a running build# SM-C105AUCUAMJ2
Please elaborate on where your dmesg is coming from.
Is it from running Saferoot to obtain Root?
Or is it from some other function you are attempting after obtaining root?
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
capt_planit said:
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
Click to expand...
Click to collapse
@ capt_planit
while I have moved on from using my [email protected] S4-Zoom, I do still have it and the dd dumps of it the problem with providing said dumps publicly is that some "idiot would inevitably flash the complete dd.image to there phone giving them an exact clone of my phone explicitly the IMEI via EFS parition are my concerns.
That being said if I know that the dd.images were to be used in a proper manner, by say a knowledgeable Dev. I would gladly supply them to further /Kickoff Development,
It sounds as if we are of like mind but I found myself at a stand still and did not recieve any response from the plea in my Sig.
But rest assured if there is something I can do to assist I will.
as far as an unbrick.img for the Zoom c105a
I did make one but have had no reason to use it to know if it works or if the SD unbrick method even works for the Zoom like it does on the Galaxy S3 that the method was originally discovered on.
Even if it does work the SD-Unbrick method only gets you to a state where Download
mode works SO unless I am mistaken and you can access adb through Download Mode witch I'm pretty sure you cant, we would still be at a stand still as there is no stock firmware publicly available for our device " Ludacris I know " but true none the less.
Edit:
1 thing we need is the OTA update from JB to KitKat available for our device we need some one to extract it before updating then and only then might we be able to create an install-able firmware for our device.
if I'm not mistaken after you download the OTA update you should be able to find it in /cache/fota just zip the entire fota folder move it to your sd-card and make it available to me and we'll make it happen from there.
If you don't want to except the update just delete it at this point and reboot.
...
...
I think this user @awwar describes an inability to access download mode>here. In anycase, I think that thread would be a great place to post your unbrick. image. I think your dd image seems too small. But if you still have it, that is what @moomoo was asking for when he started that thread. I can't provide mine, except as separate img files. My understanding is that flashing an efs image won't provide a real IMEI. I think flashing some combination of boot, system, cache (I'm surprised this would be necessary) and recovery should get the operator some kind of system. But so far it doesn't seem to work that way. Your help getting some working phone flash would be greatly appreciated. I believe, BTW that the OTA is dead...
There's a guide thread now in Guide section, use that one pls as this one isn't detailed enough and the other one has some more instructions, e.g. for backing up the files and partitions we work with!
thanks to user @Krekos/CZ/ these files are available for everyone now find them in his post here (or attached on this post) and give him a thx pls :highfive: :cyclops:
original OP text:
Im on testing sessions regarding volte and at least got that far, that the IMS server in hidden menu can be configured (wasn't accessible before my edits). but I'm stuck for now: I by accident deleted following folder which contains the modem config files for different operators. Looks like they are on the EFS partition, as a kdz and standalone-modem reflash didn't help, unfortunately:
Code:
/firmware/image/modem_pr/mcfg/configs
pls, can someone with a true H930 rooted EU OPEN phone (I've bought mine via telefonica O2 Germany) help me and zip and upload this special folder for me? would be appreciated very very much!! I don't want to find out what happens when I reboot my phone now xD maybe unfixable bootloop...
noone...? come on, this is a 3-5 minutes job deleting takes only 2 secs as i know now... but w/o these files no modem config is possible, phone could be useless on next reboot. so, pls pls...
btw: no personal data stored in these directories. there are only config files for different operators inside, nothing else. mcfg_sw.mbn files, you can google for their function and have a look at them on your phone. easiest way for zipping them would be "root explorer", it offers this function, and tar compressing too. hm, when i think about it, tar would be better format
seadersn said:
noone...? come on, this is a 3-5 minutes job deleting takes only 2 secs as i know now... but w/o these files no modem config is possible, phone could be useless on next reboot. so, pls pls...
btw: no personal data stored in these directories. there are only config files for different operators inside, nothing else. mcfg_sw.mbn files, you can google for their function and have a look at them on your phone. easiest way for zipping them would be "root explorer", it offers this function, and tar compressing too. hm, when i think about it, tar would be better format
Click to expand...
Click to collapse
I would be glad to help but I don't have H930...
hmm, which one do you own then...? maybe worth a try to have a look at the files from a different phone as long as it's native open and an EU one. and: I've seen you're a really helpful person, a superb contributor, one of the best in v30 forums thx for that! :thumbsup:
H930 here, but it's not rooted.
grmpf, there's no way then to access these files, unfortunately but thx anyway
seadersn said:
hmm, which one do you own then...? maybe worth a try to have a look at the files from a different phone as long as it's native open and an EU one. and: I've seen you're a really helpful person, a superb contributor, one of the best in v30 forums thx for that! :thumbsup:
Click to expand...
Click to collapse
maybe @SGCMarkus or @Whiskeyomega can help?
---------- Post added at 07:55 AM ---------- Previous post was at 07:46 AM ----------
myb said:
H930 here, but it's not rooted.
Click to expand...
Click to collapse
Looks like you need to get busy this weekend! Just so you actually own your phone.
I have Rooted H930. But how can i access these files?? i can't see them in TWRP.
Krekos/CZ/ said:
I have Rooted H930. But how can i access these files?? i can't see them in TWRP.
Click to expand...
Click to collapse
wonderful!! if we get this working you're my hero
in twrp there's no way to get them, this has to be done in fully booted android system. you have got terminal emulator app installed? the command would be
Code:
tar -czf /sdcard/modem.tar.gz /firmware/image/modem_pr/mcfg/configs
the resulting file can be found in root dir of sdcard then. maybe it's small enough so you can attach it on your answering post, otherwise maybe using google drive or androidfilehost is needed.
double post, sry...
It's strange but i cannot compress these files. It always tell me, i dont have privilegies for that. I try severel Emulators. I also try TotalCommander App with root privilegies, and copy the files manually, but i ended with error aswell.
ouch... did you type "su" to give the terminal emulator root privileges before trying?
I got it! I finally found emulator which compress the files. i dont know why previous apps didnt work but w/e.
Here it is: https://goo.gl/Qk293b
yay!!!!! it worked, the files are back! THANK YOU VERY VERY MUCH!!! you saved my h930 thanks again! :good::highfive::victory:
hmm, is it okay for you when i attach this zip on the first post with big fat credits to you? maybe someone else needs these mbn files for his SD835 device at some time?
I have no problem with it. you can attach it.
thx, again
...aaaand: volte (and vowifi; don't know for sure about viwifi and vt/vilte. sms over wifi/volte needs to be tested too) is up and running! LoL... o2 wasn't able to help me in four service hotline sessions and two visits in their store. really funny as they told me every time "absolutely no way, sry. we can't do this (send some infos or activate volte in account [was already activated, it worked all the time with my s7flat]), we can't do that (flash something to get this working) and so on. k, this took me an serious amount of time my kids and wife weren't really happy and proud of, but hey, there are priorities, or not? hrhr...
is there a need for a guide for everyone? maybe I get a guide up and running. problem for now is, I don't know for sure which edits are really needed and essential. this will be a guide we need to work out all together to finally see which steps are necessary for a newbie and starter. let's see, would take some time but should be possible. when five ppls in this thread are telling "yes we want this guide, let's do this together!" then I'll do it
would've not been possible w/o the help from @Krekos/CZ/ I'm really happy he helped out! :good:
I would like to try this feature and you're welcome.
Nice one. So vollte will be available for every gsm operator on stock rooted rom?